linux-kernel - Re: [PATCH 1/5] drivers: net: usb: rtl8150: bug fixing and cleanup

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20130520.004324.1700573748194578434.davem@davemloft.net>
Date:	Mon, 20 May 2013 00:43:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	petkan@...leusys.com
Cc:	romieu@...zoreil.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] drivers: net: usb: rtl8150: bug fixing and cleanup

From: Petko Manolov <petkan@...leusys.com>
Date: Mon, 20 May 2013 10:18:17 +0300 (EEST)

> On Mon, 20 May 2013, David Miller wrote:
> 
>> From: Petko Manolov <petkan@...leusys.com>
>> Date: Mon, 20 May 2013 10:09:00 +0300 (EEST)
>> 
>> > What about the .c/.h split?
>> 
>> I have no strong opinion either way.
> 
> OK, so i'll prepare new patch series that coalesce my original patch #1 
> and #2, and apply the Francois suggestion about using the generic 
> netdev_alloc_skb_ip_align() in the interrupt path.
> 
> Which tree would you want me to diff against?

As has been explained to you already, cleanups belong in 'net-next',
bug fixes belong in 'net'.

If you series has both, you have to submit them separately.  Submit
the bug fixes to 'net', then the next time I merge 'net' into 'net-next'
you can submit the cleanups on top against 'net-next'.
--
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/