From: Paolo Abeni <pabeni@redhat.com>
To: Adam Ford <aford173@gmail.com>, Jacob Keller <jacob.e.keller@intel.com>
Cc: netdev@vger.kernel.org, aford@beaconembedded.com,
Andrew Lunn <andrew@lunn.ch>,
Grygorii Strashko <grygorii.strashko@ti.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] net: ethernet: davinci_emac: Use MAC Address from Device Tree
Date: Tue, 24 Oct 2023 11:24:28 +0200 [thread overview]
Message-ID: <796915d9964d6470dc035785b83d74b8753d8ca0.camel@redhat.com> (raw)
In-Reply-To: <CAHCN7x+ttO7yLkrc80issyjum_P1rcK9d5Keoyfxa-3krz8ssg@mail.gmail.com>
On Mon, 2023-10-23 at 20:22 -0500, Adam Ford wrote:
> On Mon, Oct 23, 2023 at 7:14 PM Jacob Keller <jacob.e.keller@intel.com> wrote:
> > Looks like you didn't add the tag for which tree. Given the context, I
> > would assume net-next.
>
> That was my intent. I sent the e-mail to netdev and CC'd others. I
> thought that was enough.
For future submissions: there are 2 different netdev trees, one for new
features (net-next) and another one for bugfixes (net), and you should
specify the target explcitly in the patch prefix. See:
Documentation/process/maintainer-netdev.rst
for the more details.
Looks like this one is targeting net-next.
Cheers,
Paolo
next prev parent reply other threads:[~2023-10-24 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 15:19 [PATCH V2] net: ethernet: davinci_emac: Use MAC Address from Device Tree Adam Ford
2023-10-24 0:14 ` Jacob Keller
2023-10-24 1:22 ` Adam Ford
2023-10-24 9:24 ` Paolo Abeni [this message]
2023-10-24 9:30 ` patchwork-bot+netdevbpf
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=796915d9964d6470dc035785b83d74b8753d8ca0.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=grygorii.strashko@ti.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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).