public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 24 Apr 2010 03:24:17 +0200	[thread overview]
Message-ID: <4BD24841.1010206@VirtualLogix.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1004231402180.1777-100000@iolanthe.rowland.org>

On 04/23/2010 08:04 PM, Alan Stern wrote:
> On Fri, 23 Apr 2010, Eric Lescouet wrote:
> 
>> Well, most of the files include hcd.h (which includes hub.h),
>> only ~4 of them directly use hub.h.
> 
> Oh.  Okay, that makes life easier.  Probably some of the files which 
> include hub.h directly also include hcd.h.
> 
>> So what's your vote? rename hub.h into ch11.h?
> 
> Yeah, go ahead.  I like the idea of the kernel containing information 
> about Chapter 11.  (Although I haven't heard of anyone yet going 
> bankrupt as a result of using Linux...)
> 
> Alan Stern
> 

It looks like couple of files in drivers/usb/core and usb/host have been
modified already in latest snapshot (2.6.34-rc5-git5).
Is it still ok to provide the patches against the mainline (2.6.34-rc5)
or should I do it against the snapshot (2.6.34-rc5-git5)?

Thanks,
	Eric.

  reply	other threads:[~2010-04-24  1:24 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
2010-04-23 18:04             ` Alan Stern
2010-04-24  1:24               ` Eric Lescouet [this message]
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=4BD24841.1010206@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