From: Jakub Kicinski <kuba@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH wpan-next 1/2] MAINTAINERS: Update wpan tree
Date: Tue, 11 Apr 2023 13:02:09 -0700 [thread overview]
Message-ID: <20230411130209.6ffe1d21@kernel.org> (raw)
In-Reply-To: <20230411090122.419761-1-miquel.raynal@bootlin.com>
On Tue, 11 Apr 2023 11:01:21 +0200 Miquel Raynal wrote:
> The wpan maintainers group is switching from Stefan's tree to a group
> tree called 'wpan'. We will now maintain:
> * wpan/wpan.git master:
> Fixes targetting the 'net' tree
> * wpan/wpan-next.git master:
> Features targetting the 'net-next' tree
> * wpan/wpan-next.git staging:
> Same as the wpan-next master branch, but we will push there first,
> expecting robots to parse the tree and report mistakes we would have
> not catch. This branch can be rebased and force pushed, unlike the
> others.
Very nice, feel free to ship these two with fixes.
We often fast track MAINTAINERS updates.
next prev parent reply other threads:[~2023-04-11 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 9:01 [PATCH wpan-next 1/2] MAINTAINERS: Update wpan tree Miquel Raynal
2023-04-11 9:01 ` [PATCH wpan-next 2/2] MAINTAINERS: Add wpan patchwork Miquel Raynal
2023-04-11 12:13 ` Alexander Aring
2023-04-12 19:50 ` Stefan Schmidt
2023-04-11 12:11 ` [PATCH wpan-next 1/2] MAINTAINERS: Update wpan tree Alexander Aring
2023-04-12 19:50 ` Stefan Schmidt
2023-04-11 20:02 ` Jakub Kicinski [this message]
2023-04-12 19:51 ` Stefan Schmidt
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=20230411130209.6ffe1d21@kernel.org \
--to=kuba@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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).