[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180111.120725.1401336309660096435.davem@davemloft.net>
Date: Thu, 11 Jan 2018 12:07:25 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: lipeng321@...wei.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxarm@...wei.com, salil.mehta@...wei.com
Subject: Re: [PATCH net-next 00/11] add some new features and fix some bugs
From: Peng Li <lipeng321@...wei.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.
Thank you.
Powered by blists - more mailing lists