netdev - Re: [PATCHv2] gro: Name the GRO result enumeration type

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: <20091029.213223.94736944.davem@davemloft.net>
Date:	Thu, 29 Oct 2009 21:32:23 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: [PATCHv2] gro: Name the GRO result enumeration type

From: Ben Hutchings <bhutchings@...arflare.com>
Date: Thu, 29 Oct 2009 18:26:15 +0000

> This clarifies which return and parameter types are GRO result codes
> and not RX result codes.
> 
> Signed-off-by: Ben Hutchings <bhutchings@...arflare.com>
> ---
> This replaces the previous patch 1/4 and avoids introducing compiler
> warnings.  The original patches 2-4 will still apply on top of it.

You can't do this Ben.

Changing this patch makes the follow-on patches not apply cleanly.

So if you respin stuff like this, you have to respin the follow-on
patches too.

I'll fix this up, but I am so irritated that I've wasted so much time
tonight already on patch submissions that were not handled with any
care at all.  And it's all at my expense.
--
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