From: Dan Murphy <dmurphy@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <andrew@lunn.ch>, <f.fainelli@gmail.com>, <hkallweit1@gmail.com>,
<bunk@kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<grygorii.strashko@ti.com>
Subject: Re: [PATCH net-next v2 0/2] Rebase of patches
Date: Mon, 9 Dec 2019 12:23:46 -0600 [thread overview]
Message-ID: <898c9346-311e-4c93-9f83-afe255b54243@ti.com> (raw)
In-Reply-To: <20191209.101005.1980841296607612612.davem@davemloft.net>
David
On 12/9/19 12:10 PM, David Miller wrote:
> From: Dan Murphy <dmurphy@ti.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
next prev parent reply other threads:[~2019-12-09 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 17:59 [PATCH net-next v2 0/2] Rebase of patches Dan Murphy
2019-12-09 17:59 ` [PATCH net-next v2 1/2] dt-bindings: dp83867: Convert fifo-depth to common fifo-depth and make optional Dan Murphy
2019-12-09 17:59 ` [PATCH net-next v2 2/2] net: phy: dp83867: Add rx-fifo-depth and tx-fifo-depth Dan Murphy
2019-12-09 18:10 ` [PATCH net-next v2 0/2] Rebase of patches David Miller
2019-12-09 18:23 ` Dan Murphy [this message]
2019-12-09 18:31 ` David Miller
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=898c9346-311e-4c93-9f83-afe255b54243@ti.com \
--to=dmurphy@ti.com \
--cc=andrew@lunn.ch \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).