From: "lipeng (Y)" <lipeng321@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <salil.mehta@huawei.com>
Subject: Re: [PATCH net-next 00/11] add some new features and fix some bugs
Date: Fri, 12 Jan 2018 11:26:53 +0800 [thread overview]
Message-ID: <d8e6fde9-6089-bf71-438e-5263758f3474@huawei.com> (raw)
In-Reply-To: <20180111.120725.1401336309660096435.davem@davemloft.net>
On 2018/1/12 1:07, David Miller wrote:
> From: Peng Li <lipeng321@huawei.com>
> Date: Thu, 11 Jan 2018 19:45:55 +0800
>
>> This patchset adds some new features and fixes some bugs:
>> [patch 1/11] adds ethtool_ops.get_channels support for VF.
>> [patch 2/11] removes TSO config command from VF driver.
>> [patch 3/11] adds ethtool_ops.get_coalesce support to PF.
>> [patch 4/11] adds ethtool_ops.set_coalesce support to PF.
>> [patch 5/11 - 11/11] do some code improvements and fix some bugs.
> Can you please write a real commit message in your header postings
> please?
>
> Don't just copy the subject lines from the patches, and add one
> sentence with a brief description.
>
> Really write real paragraphs describing what the patch series
> is doing, how it is doing it, and why it is doing it that
> way.
>
> A real explanation that tells the reader what exactly to
> expect when they review the patches themselves.
Thanks for your advice.
A detail explanation is better for review, I will write
the "real explanation" in V2 patch-set.
Peng Li
> Thank you.
>
> .
prev parent reply other threads:[~2018-01-12 3:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 11:45 Peng Li
2018-01-11 11:45 ` [PATCH net-next 01/11] net: hns3: add ethtool_ops.get_channels support for VF Peng Li
2018-01-11 11:45 ` [PATCH net-next 02/11] net: hns3: remove TSO config command from VF driver Peng Li
2018-01-11 11:45 ` [PATCH net-next 03/11] net: hns3: add ethtool_ops.get_coalesce support to PF Peng Li
2018-01-11 11:45 ` [PATCH net-next 04/11] net: hns3: add ethtool_ops.set_coalesce " Peng Li
2018-01-11 11:46 ` [PATCH net-next 05/11] net: hns3: refactor interrupt coalescing init function Peng Li
2018-01-11 11:46 ` [PATCH net-next 06/11] net: hns3: refactor GL update function Peng Li
2018-01-11 11:46 ` [PATCH net-next 07/11] net: hns3: remove unused GL setup function Peng Li
2018-01-11 11:46 ` [PATCH net-next 08/11] net: hns3: change the unit of GL value macro Peng Li
2018-01-11 11:46 ` [PATCH net-next 09/11] net: hns3: add int_gl_idx setup for TX and RX queues Peng Li
2018-01-11 11:46 ` [PATCH net-next 10/11] net: hns3: add feature check when feature changed Peng Li
2018-01-11 11:46 ` [PATCH net-next 11/11] net: hns3: check for NULL function pointer in hns3_nic_set_features Peng Li
2018-01-11 17:07 ` [PATCH net-next 00/11] add some new features and fix some bugs David Miller
2018-01-12 3:26 ` lipeng (Y) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8e6fde9-6089-bf71-438e-5263758f3474@huawei.com \
--to=lipeng321@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®