[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <898c9346-311e-4c93-9f83-afe255b54243@ti.com>
Date: Mon, 9 Dec 2019 12:23:46 -0600
From: Dan Murphy <dmurphy@...com>
To: David Miller <davem@...emloft.net>
CC: <andrew@...n.ch>, <f.fainelli@...il.com>, <hkallweit1@...il.com>,
<bunk@...nel.org>, <netdev@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<grygorii.strashko@...com>
Subject: Re: [PATCH net-next v2 0/2] Rebase of patches
David
On 12/9/19 12:10 PM, David Miller wrote:
> From: Dan Murphy <dmurphy@...com>
> Date: Mon, 9 Dec 2019 11:59:41 -0600
>
>> This is a rebase of the dp83867 patches on top of the net-next tree
> That's not what this patch series does.
>
> The introductory posting is where you describe, at a high level, what the
> whole patch series is doing as a unit, how it is doing it, and why it is
> doing it that way.
>
> It also serves as the single email I can respond to when I want to let you
> know that I've applied the patch series.
>
> Please read the documentation under Documentation/ if you still are unsure
> what this introductory posting is all about and how you should compose one.
>
> Thank you.
I understand what a cover letter is.
I don't normally see cover letters required for small patchsets like
this in other trees. The commit messages should explain in detail what
is being changed as the cover letters are not committed to the kernel.
I only add cover letters when the patchsets are significant, per the
Documentation/ you eluded to.
But if you require this for the linux net tree then I can add them as I
move forward it is not a problem either way.
Dan
Powered by blists - more mailing lists