From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next v6 0/3] Incorporated all required changes Date: Tue, 07 Nov 2017 08:45:35 +0900 (KST) Message-ID: <20171107.084535.1468386023963515204.davem@davemloft.net> References: <1509724159-5559-1-git-send-email-manish.kurup@verizon.com> <20171105.220843.222678154572186350.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us, jakub.kicinski@netronome.com, pieter.jansenvanvuuren@netronome.com, simon.horman@netronome.com, john.hurley@netronome.com, aring@mojatatu.com, mrv@mojatatu.com, manish.kurup@verizon.com, netdev@vger.kernel.org, oss-drivers@netronome.com To: kurup.manish@gmail.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:39528 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754594AbdKFXpk (ORCPT ); Mon, 6 Nov 2017 18:45:40 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Manish Kurup Date: Mon, 6 Nov 2017 11:52:37 -0500 > Currently, the body of the commit message describes what it is doing > in each commit patch. Would you like me to add some detail to the > description of each commit? This is not what I am asking for. The header posting for a patch series serves a very important purpose. It tells the reader at a high level what the patch series is doing as a whole, how it is doing it, and why it is doing it that way.