From: Jakub Kicinski <kuba@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH net-next 6/6] MAINTAINERS: Add entry for XFRM documentation
Date: Thu, 30 Oct 2025 08:44:12 -0700 [thread overview]
Message-ID: <20251030084412.5f4dc096@kernel.org> (raw)
In-Reply-To: <20251030084158.61455ddc@kernel.org>
On Thu, 30 Oct 2025 08:41:58 -0700 Jakub Kicinski wrote:
> On Thu, 30 Oct 2025 09:12:35 +0100 Steffen Klassert wrote:
> > On Wed, Oct 29, 2025 at 03:26:14PM +0700, Bagas Sanjaya wrote:
> > > XFRM patches are supposed to be sent to maintainers under "NETWORKING
> > > [IPSEC]" heading, but it doesn't cover XFRM docs yet. Add the entry.
> > >
> > > Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> > > ---
> > > MAINTAINERS | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index d652f4f27756ef..4f33daad40bed6 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -18041,6 +18041,7 @@ L: netdev@vger.kernel.org
> > > S: Maintained
> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git
> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
> > > +F: Documentation/networking/xfrm/
> >
> > That means that I'm now responsible for this.
> > But I'm OK with it if nobody has objections on it.
>
> Definitely no objections :)
> Let me mark this series as "Awaiting Upstream".
I take back the "Awaiting Upstream" part. This set conflicts with
the big ToC tree reorg patch. Let's either merge this into net-next
or wait for trees to re-sync?
Not a big deal but the conflict is easily avoidable ...
next prev parent reply other threads:[~2025-10-30 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:26 [PATCH net-next 0/6] xfrm docs update Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 1/6] Documentation: xfrm_device: Wrap iproute2 snippets in literal code block Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 2/6] Documentation: xfrm_device: Use numbered list for offloading steps Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 3/6] Documentation: xfrm_device: Separate hardware offload sublists Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 4/6] Documentation: xfrm_sync: Properly reindent list text Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 5/6] net: Move XFRM documentation into its own subdirectory Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 6/6] MAINTAINERS: Add entry for XFRM documentation Bagas Sanjaya
2025-10-30 8:12 ` Steffen Klassert
2025-10-30 15:41 ` Jakub Kicinski
2025-10-30 15:44 ` Jakub Kicinski [this message]
2025-10-31 0:12 ` Bagas Sanjaya
2025-10-31 0:51 ` Jakub Kicinski
2025-11-01 4:58 ` [PATCH net-next 0/6] xfrm docs update Randy Dunlap
2025-11-01 9:14 ` Bagas Sanjaya
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=20251030084412.5f4dc096@kernel.org \
--to=kuba@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
/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).