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: <20130501.131602.899596493606702378.davem@davemloft.net>
Date:	Wed, 01 May 2013 13:16:02 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	gerlando.falauto@...mile.com
Cc:	netdev@...r.kernel.org, sergei.shtylyov@...entembedded.com,
	jon.maloy@...csson.com, erik.hugne@...csson.com,
	ying.xue@...driver.com, holger.brunck@...mile.com
Subject: Re: [PATCH v3b 1/3] tipc: cosmetic: clean up comments and break a
 long line

From: Gerlando Falauto <gerlando.falauto@...mile.com>
Date: Wed,  1 May 2013 18:41:17 +0200

> Signed-off-by: Gerlando Falauto <gerlando.falauto@...mile.com>
> ---
> Changes from v3:
> * Added "and break a long line" to the commit message
> Changes from v2:
> * Split cosmetic (this patch) from functional changes (next patch)

Never resubmit patches by themselves, always resubmit the entire series.

Because when one patch has problems, I toss the entire series from patchwork,
and by resubmitting the entire series again you are also giving me important
information, you're telling me that the subsequent patches in the series
still apply cleanly even though the first one has changed.

I've tossed this patch too, resubmit this properly, thanks.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ