From: Eric Lescouet <Eric.Lescouet@VirtualLogix.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
"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 19:51:44 +0200 [thread overview]
Message-ID: <4BD1DE30.5030405@VirtualLogix.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1004231246440.1777-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Fri, 23 Apr 2010, Eric Lescouet wrote:
>
>> 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?
>
> Two files. The first would be ch11.h (or maybe keep the name hub.h;
> I'm not sure which is best), and the second would be hcd.h (including
> the leftover parts from the original hub.h).
>
OK. understood now ;-)
>> 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?
>
> If it weren't for the rename, I'd say do it in two patches. But if the
> name is changed to ch11.h then those 40 files would have to be altered
> twice.
>
> Alan Stern
>
Well, most of the files include hcd.h (which includes hub.h),
only ~4 of them directly use hub.h.
So what's your vote? rename hub.h into ch11.h?
Eric.
next prev parent reply other threads:[~2010-04-23 17:52 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
2010-04-23 16:37 ` Greg KH
2010-04-23 16:50 ` Alan Stern
2010-04-23 17:51 ` Eric Lescouet [this message]
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=4BD1DE30.5030405@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