From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [RFC v3 1/1] net/hsr: Add support for IEC 62439-3 High-availability Seamless Redundancy Date: Thu, 16 Aug 2012 14:46:25 -0700 (PDT) Message-ID: <20120816.144625.603156941302668648.davem@davemloft.net> References: <502D475C.9090208@xdin.com> <20120816.133036.1422214989121265534.davem@davemloft.net> <502D6332.1030303@xdin.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, joe@perches.com, shemminger@vyatta.com, kuznet@ms2.inr.ac.ru, jboticario@gmail.com, balferreira@googlemail.com To: Arvid.Brodin@xdin.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:35672 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756356Ab2HPVq3 (ORCPT ); Thu, 16 Aug 2012 17:46:29 -0400 In-Reply-To: <502D6332.1030303@xdin.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Arvid Brodin 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.