public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Mina Almasry <almasrymina@google.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
	Feng zhou <zhoufeng.zf@bytedance.com>,
	axboe@kernel.dk,  dtatulea@nvidia.com, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org,  yangzhenze@bytedance.com,
	wangdongdong.6@bytedance.com
Subject: Re: [PATCH net-next] io_uring/zcrx: fix ifq->if_rxq is -1, get dma_dev is NULL
Date: Fri, 12 Sep 2025 11:30:11 -0700	[thread overview]
Message-ID: <CAHS8izOCc9-MydM6xDO8SsVs1bAZWuKcCWSJv_t0AsJznGnipA@mail.gmail.com> (raw)
In-Reply-To: <20250912072232.5019e894@kernel.org>

On Fri, Sep 12, 2025 at 7:22 AM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Fri, 12 Sep 2025 13:40:06 +0100 Pavel Begunkov wrote:
> > On 9/12/25 09:39, Feng zhou wrote:
> > > From: Feng Zhou <zhoufeng.zf@bytedance.com>
> > >
> > > ifq->if_rxq has not been assigned, is -1, the correct value is
> > > in reg.if_rxq.
> >
> > Good catch. Note that the blamed patch was merged via the net tree
> > this time around to avoid conflicts, and the io_uring tree doesn't
> > have it yet. You can repost it adding netdev@vger.kernel.org and
> > the net maintainers to be merged via the net tree. Otherwise it'll
> > have to wait until 6.18-rc1 is out
>
> If only we had a maintainers entry that makes people automatically
> CC both lists, eh? :\

FWIW that was the intention behind this patch I sent:

https://lore.kernel.org/netdev/20250821025620.552728-1-almasrymina@google.com/

I didn't get any feedback on it; I assumed people are not interested
(enough). Let me know if you want me to press the issue and send a
non-RFC version.

Although that one made sure that the changes are sent to net, only. I
guess I could add the io_uring list to the L entries.


--
Thanks,
Mina

  reply	other threads:[~2025-09-12 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12  8:39 [PATCH net-next] io_uring/zcrx: fix ifq->if_rxq is -1, get dma_dev is NULL Feng zhou
2025-09-12 12:40 ` Pavel Begunkov
2025-09-12 13:54   ` [External] " Feng Zhou
2025-09-12 14:22   ` Jakub Kicinski
2025-09-12 18:30     ` Mina Almasry [this message]
2025-09-15 15:14     ` Pavel Begunkov
  -- strict thread matches above, loose matches on Subject: below --
2025-09-12 14:01 Feng zhou
2025-09-15 19:36 ` Jens Axboe
2025-09-16  1:30 ` patchwork-bot+netdevbpf

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=CAHS8izOCc9-MydM6xDO8SsVs1bAZWuKcCWSJv_t0AsJznGnipA@mail.gmail.com \
    --to=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dtatulea@nvidia.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangdongdong.6@bytedance.com \
    --cc=yangzhenze@bytedance.com \
    --cc=zhoufeng.zf@bytedance.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