[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191209.103119.563197602023949500.davem@davemloft.net>
Date: Mon, 09 Dec 2019 10:31:19 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: dmurphy@...com
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
From: Dan Murphy <dmurphy@...com>
Date: Mon, 9 Dec 2019 12:23:46 -0600
> I understand what a cover letter is.
As seen below, perhaps you don't
> The commit messages should explain in detail
> what is being changed as the cover letters are not committed to the
> kernel.
Not true.
I _always_ add them, for every networking patch series.
They go into the merge commit I create for your patch series.
Powered by blists - more mailing lists