linux-kernel - Re: USBIP (staging) driver's dependency on drivers/usb/core internal headers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BD24841.1010206@VirtualLogix.com>
Date:	Sat, 24 Apr 2010 03:24:17 +0200
From:	Eric Lescouet <Eric.Lescouet@...tualLogix.com>
To:	Greg KH <greg@...ah.com>
CC:	Alan Stern <stern@...land.harvard.edu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>
Subject: Re: USBIP (staging) driver's dependency on drivers/usb/core internal
 headers

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/