Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
6caf5656
Commit
6caf5656
authored
May 29, 2002
by
Patrick Mochel
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
USB: Move configuration parsing code from usb.c to config.c
parent
1a2f7297
Changes
3
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
497 additions
and
489 deletions
+497
-489
drivers/usb/core/Makefile
drivers/usb/core/Makefile
+3
-2
drivers/usb/core/config.c
drivers/usb/core/config.c
+494
-0
drivers/usb/core/usb.c
drivers/usb/core/usb.c
+0
-487
No files found.
drivers/usb/core/Makefile
View file @
6caf5656
...
@@ -2,9 +2,10 @@
...
@@ -2,9 +2,10 @@
# Makefile for USB Core files and filesystem
# Makefile for USB Core files and filesystem
#
#
export-objs
:=
usb.o hcd.o urb.o message.o
export-objs
:=
usb.o hcd.o urb.o message.o
config.o
usbcore-objs
:=
usb.o usb-debug.o hub.o hcd.o urb.o message.o
usbcore-objs
:=
usb.o usb-debug.o hub.o hcd.o urb.o message.o
\
config.o
ifeq
($(CONFIG_USB_DEVICEFS),y)
ifeq
($(CONFIG_USB_DEVICEFS),y)
usbcore-objs
+=
devio.o inode.o drivers.o devices.o
usbcore-objs
+=
devio.o inode.o drivers.o devices.o
...
...
drivers/usb/core/config.c
0 → 100644
View file @
6caf5656
This diff is collapsed.
Click to expand it.
drivers/usb/core/usb.c
View file @
6caf5656
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment