netdev - Re: [RFC v3 1/1] net/hsr: Add support for IEC 62439-3 High-availability Seamless Redundancy

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]

Date:	Thu, 16 Aug 2012 14:46:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Arvid.Brodin@...n.com
Cc:	netdev@...r.kernel.org, joe@...ches.com, shemminger@...tta.com,
	kuznet@....inr.ac.ru, jboticario@...il.com,
	balferreira@...glemail.com
Subject: Re: [RFC v3 1/1] net/hsr: Add support for IEC 62439-3
 High-availability Seamless Redundancy

From: Arvid Brodin <Arvid.Brodin@...n.com>
Date: Thu, 16 Aug 2012 21:16:34 +0000

> On 2012-08-16 22:30, David Miller wrote:
>> 
>> This is not the correct way to post a patch.
>> 
>> You should provide a proper full Subject: and commit message text in
>> the body of the email before the patch itself.
> 
> I fail to see what's missing from the Subject: line; please elaborate.

You left in the "Re: " etc. prefix.  You should never post new versions
of a patch as a reply, you should make new, fresh, mailing list postings.

And you failed to include the commit message body.  Everything you seem
to thing belongs in the "0/1" posting, at a minimum actually belongs
here in 1/1 too.
--
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