From: Jakub Kicinski <kuba@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Aryan Arora <aryanarora.w1@gmail.com>,
Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
David Girault <david.girault@qorvo.com>,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+19cbce4cc656ecd4febc@syzkaller.appspotmail.com
Subject: Re: [PATCH] mac802154: Cancel scan work synchronously during hardware teardown
Date: Mon, 16 Nov 2026 14:11:14 -0800 [thread overview]
Message-ID: <20261116141114.30ead071@kernel.org> (raw)
In-Reply-To: <87a4n8rczw.fsf@bootlin.com>
On Mon, 16 Nov 2026 16:51:15 +0100 Miquel Raynal wrote:
> I believe the flow that works best is if you (net maintainers)
> "continue" applying the patches directly, especially since these days
> there are only AI bug fixes. We can definitely re-instate a formal
> pull-request relationship between us as soon as there are new "features"
> being discussed. We (wpan folks) will do our best to respond with timely
> feedback/reviews.
Alright, we have a lot of patches to handle so having more help
(IOW having someone else handle the patches fully) would be preferable.
But if you review in a timely fashion we can handle the manual labor
parts.
FWIW you can use the "Maintainer" filter on this page to quickly
https://netdev-ctrl.bots.linux.dev/suie.html?delegate=netdev
find outstanding patches to your subsystem.
next prev parent reply other threads:[~2026-11-16 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 12:09 [PATCH] mac802154: Cancel scan work synchronously during hardware teardown Aryan Arora
2026-10-12 17:00 ` Miquel Raynal
2026-10-20 2:07 ` Jakub Kicinski
2026-11-16 15:51 ` Miquel Raynal
2026-11-16 22:11 ` Jakub Kicinski [this message]
2026-10-13 12:52 ` netdev-bot+sashiko
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=20261116141114.30ead071@kernel.org \
--to=kuba@kernel.org \
--cc=alex.aring@gmail.com \
--cc=aryanarora.w1@gmail.com \
--cc=davem@davemloft.net \
--cc=david.girault@qorvo.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
--cc=syzbot+19cbce4cc656ecd4febc@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.