netdev - Re: [PATCH 5/5] net-next:asix: update VERSION and white space changes

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: <CANEJEGstEcWx=WD5ZfBrErOpzi+PTQys1hF0scPdVADwQFY+Yw@mail.gmail.com>
Date:	Mon, 14 Nov 2011 16:39:13 -0800
From:	Grant Grundler <grundler@...omium.org>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	allan@...x.com.tw, freddy@...x.com.tw
Subject: Re: [PATCH 5/5] net-next:asix: update VERSION and white space changes

On Mon, Nov 14, 2011 at 3:42 PM, David Miller <davem@...emloft.net> wrote:
> From: Grant Grundler <grundler@...omium.org>
> Date: Mon, 14 Nov 2011 15:22:01 -0800
>
>> No functional changes. Three things targeted:
>> o update VERSION to reflect previous changes.
>> o fix up white space/formatting of some lines
>> o define 150 to be AX_SWRESET_MDELAY (self documenting code)
>>
>> Signed-off-by: Grant Grundler <grundler@...omium.org>
>
> Why have such a wonderful set of real bug fixes that I can apply right
> now and send off to Linus's tree, only to sabotage it with whitespace
> changes at the end which are no appropriate?
>
> Please, just submit this without the whitespace and other cleanup
> stuff.  Restrict it to real bug fixes, and I'll push it around.

No Problem! :)

I wasn't expecting this to go to linus immediately but it makes that it should.

> The whitespace and other bits can be submitted for net-next afterwards.

Will do.

cheers,
grant
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html