linux-kernel - Re: [PATCH 4/6] netprio_cgroup: use IS

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: <20120201.020738.1965865410881089752.davem@davemloft.net>
Date:	Wed, 01 Feb 2012 02:07:38 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	lizf@...fujitsu.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	cgroups@...r.kernel.org, nhorman@...driver.com
Subject: Re: [PATCH 4/6] netprio_cgroup: use IS_ENABLED() and family

From: Li Zefan <lizf@...fujitsu.com>
Date: Wed, 01 Feb 2012 15:06:53 +0800

> 14:59, David Miller wrote:
>> 
>> Do not mix genuine bug fixes and cleanups.
>> 
>> Otherwise I cannot apply your bug fixes to the 'net' tree.
>> 
>> Seperate things out, submit only pure bug fixes first, then
>> later once those changes propagate you can submit the cleanups.
>> 
> 
> I did seperate them out, so the first three patches are fixes,
> and others are cleanups. I can resend cleanup patches once
> fixes hit mainline.

Seperate them in different groups, don't submit them as one
collection.  And definitely don't submit them all at the
same damn time!  You have to wait with the dependent cleanups
until the fixes go in, and subsequently show up in my net-next
tree.

I'm not applying this stuff until you submit it properly, in
two stages.
--
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/