From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
bpf@vger.kernel.org, dsahern@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next] docs: netdev: fix iproute2 process documentation
Date: Thu, 05 Nov 2026 08:46:22 -0500 [thread overview]
Message-ID: <willemdebruijn.kernel.213e1d84478e4@gmail.com> (raw)
In-Reply-To: <20261105143049.51af15a1@stephen-xps.local>
Stephen Hemminger wrote:
> On Tue, 03 Nov 2026 09:44:53 -0500
> Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote:
>
> > Stephen Hemminger wrote:
> > > On Mon, 2 Nov 2026 22:35:56 -0500
> > > Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote:
> > >
> > > > +
> > > > +Patches are tracked in patchwork under the netdevbpf project and delegated
> > > > +to 'shemminger' for further processing:
> > > > +
> > >
> > > Minor nit. David Ahern (dsa) handles the iproute-next patches.
> > > I stick to only iproute.
> >
> > I know, but there is no separate delegation in patchwork to David.
> >
> > I assumed all iproute2 patches would get delegated to your patchwork
> > component. Is this not correct?
>
> Right now we correct it manually. Often patches target the wrong tree.
This is not about the trees, but delegate on patchwork. There is no
delegate dsahern in the dropdown menu.
next prev parent reply other threads:[~2026-11-05 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 3:35 [PATCH net-next] docs: netdev: fix iproute2 process documentation Willem de Bruijn
2026-11-03 4:30 ` Alexei Starovoitov
2026-11-03 8:22 ` Stephen Hemminger
2026-11-03 14:44 ` Willem de Bruijn
2026-11-05 13:30 ` Stephen Hemminger
2026-11-05 13:46 ` Willem de Bruijn [this message]
2026-11-05 14:45 ` Stephen Hemminger
2026-11-05 14:56 ` Willem de Bruijn
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=willemdebruijn.kernel.213e1d84478e4@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--cc=willemb@google.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