From: Jakub Kicinski <kuba@kernel.org>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: Paolo Abeni <pabeni@redhat.com>,
Marek Lindner <marek.lindner@mailbox.org>,
Simon Wunderlich <sw@simonwunderlich.de>,
Antonio Quartulli <antonio@mandelbit.com>,
Sven Eckelmann <sven@narfation.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] batman-adv: fix duplicate MAC address check
Date: Thu, 10 Apr 2025 17:39:58 -0700 [thread overview]
Message-ID: <20250410173958.788611a1@kernel.org> (raw)
In-Reply-To: <94e1ac2c-46f1-4787-ad50-e4a5ab11011a@universe-factory.net>
On Thu, 10 Apr 2025 17:38:30 +0200 Matthias Schiffer wrote:
> >> Fixes: c6c8fea29769 ("net: Add batman-adv meshing protocol")
> >> Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
> >
> > Even if marked for net I assume this will eventually go first via the
> > batman tree.
>
> Yes. Should I have marked this differently?
Yes, let's reserve net for patches which will go directly into:
https://web.git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/
Similar for net-next.
The tree name is supposed to tell the maintainer who you expect
to take the patch.
The batman tree (according to MAINTAINERS) is called linux-merge
so let's ignore that and use batman and batman-next?
prev parent reply other threads:[~2025-04-11 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 16:30 [PATCH net] batman-adv: fix duplicate MAC address check Matthias Schiffer
2025-04-10 9:38 ` Paolo Abeni
2025-04-10 15:38 ` Matthias Schiffer
2025-04-11 0:39 ` Jakub Kicinski [this message]
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=20250410173958.788611a1@kernel.org \
--to=kuba@kernel.org \
--cc=antonio@mandelbit.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.lindner@mailbox.org \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
/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).