From: Eric Lescouet <Eric.Lescouet@VirtualLogix.com>
To: Greg KH <greg@kroah.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: USBIP (staging) driver's dependency on drivers/usb/core internal headers
Date: Fri, 23 Apr 2010 18:31:28 +0200 [thread overview]
Message-ID: <4BD1CB60.20209@VirtualLogix.com> (raw)
In-Reply-To: <20100423161455.GA21129@kroah.com>
Greg KH wrote:
> On Fri, Apr 23, 2010 at 11:52:26AM -0400, Alan Stern wrote:
>> On Fri, 23 Apr 2010, Greg KH wrote:
>>
>>> On Fri, Apr 23, 2010 at 12:44:11PM +0200, Eric Lescouet wrote:
>>>> Hi,
>>>>
>>>> The USBIP modules (and some others) have a direct dependency on the following headers:
>>>> - drivers/usb/core/hdc.h (struct usb_hcd and various routines)
>>>> - drivers/usb/core/hub.h (couple of constants)
>>>> Because those headers are not part of include/, it makes it quite difficult
>>>> to compile them as standalone modules (e.g.: against pre-compiled kernel).
>>> Then don't do that :)
>>>
>>>> hdc.c and hub.c are relatively self-contained and could be moved to e.g.: include/linux/usb/.
>>>>
>>>> What do you think?
>>> I think the code needs to be cleaned up and merged to the main part of
>>> the kernel tree, then this wouldn't be an issue, right?
>> I think moving hub.h into include/linux/usb would be a good thing.
>> However, if this is done then the file contents should be rearranged
>> slightly:
>>
>> Everything from the "Hub request types" comment through the
>> various HUB_TTTT_* definitions (except the line declaring
>> struct usb_device) should be extracted into a separate file.
>> This new file could be called ch11.h (because it contains
>> constants and structures from Chapter 11 of the USB 2.0 spec,
>> just as ch9.h contains information from Chapter 9) or it
>> could keep the name hub.h. It could even be exported as
>> a userspace header file.
>>
>> The remainder (not very much) should be merged into hcd.h.
>>
>> Once that's done, moving hcd.h into include/linux/usb would be a
>> reasonable thing to do as well. It is shared between usbcore and the
>> HCDs, so it really does belong in a more public location.
>
> Ok, fair enough. Patches are always welcome :)
>
> thanks,
>
> greg k-h
If I understand correctly, splitting hub.h into hub.h + ch11.h is
independent of the move. At the end the 2 (or 3 files) would end up
into include/linux/usb/.
correct?
I've tried to move hub.h and hcd.h and to compile the kernel, already.
Changing the path of the #include directives in ~40 files did the trick.
Would you like 2 patches (move and then split) or only 1?
Thanks,
Eric.
next prev parent reply other threads:[~2010-04-23 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 10:44 USBIP (staging) driver's dependency on drivers/usb/core internal headers Eric Lescouet
2010-04-23 15:07 ` Greg KH
2010-04-23 15:52 ` Alan Stern
2010-04-23 16:14 ` Greg KH
2010-04-23 16:31 ` Eric Lescouet [this message]
2010-04-23 16:37 ` Greg KH
2010-04-23 16:50 ` Alan Stern
2010-04-23 17:51 ` Eric Lescouet
2010-04-23 18:04 ` Alan Stern
2010-04-24 1:24 ` Eric Lescouet
2010-04-24 15:17 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD1CB60.20209@VirtualLogix.com \
--to=eric.lescouet@virtuallogix.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox