From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>
Subject: Re: [PATCH] idpf: Replace use of system_unbound_wq with system_dfl_wq
Date: Mon, 16 Mar 2026 12:41:07 -0700 [thread overview]
Message-ID: <20260316124107.0dd3cc2b@kernel.org> (raw)
In-Reply-To: <878cd07a-b7fb-491a-9cec-8ddbab2bb13b@intel.com>
On Mon, 16 Mar 2026 09:58:29 -0700 Tony Nguyen wrote:
> On 3/14/2026 9:10 AM, Jakub Kicinski wrote:
> > On Fri, 13 Mar 2026 17:08:57 +0100 Przemek Kitszel wrote:
> >> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> >
> > Process question - even tho you are also a maintainer I only read
> > Tony's tags as "please apply directly". LMK if that's right, I'll
> > try to remember / make a note..
>
> I talked to Przemek about this a little this morning. Since the
> Reviewed-by tag is used more prevalently in our process, perhaps an
> Acked-by could mean take this directly and the Reviewed-by keeps the
> same process of going through IWL. Other thought would be to explicitly
> ask/state for it to get taken directly. Open to other ideas as well if
> there's something else you'd prefer.
Sounds complicated :S Let me continue ignoring Przemek's tags for the
purpose of direct application. I guess it's more about who sends the
PRs than who is a maintainer. If you send PRs I naturally never see
your review tags, as the patches will eventually come out with your SoB.
prev parent reply other threads:[~2026-03-16 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 15:09 [PATCH] idpf: Replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2026-03-13 16:08 ` Przemek Kitszel
2026-03-14 16:10 ` Jakub Kicinski
2026-03-16 16:58 ` Tony Nguyen
2026-03-16 19:41 ` 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=20260316124107.0dd3cc2b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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