public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: David Wei <dw@davidwei.uk>,
	io-uring@vger.kernel.org, netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>, Mina Almasry <almasrymina@google.com>
Subject: Re: [PATCH 1/1] io_uring zcrx: add MAINTAINERS entry
Date: Wed, 22 Oct 2025 12:38:56 +0100	[thread overview]
Message-ID: <60d18b98-6a25-4db7-a4c6-0c86d6c4f787@gmail.com> (raw)
In-Reply-To: <20251021202944.3877502-1-dw@davidwei.uk>

On 10/21/25 21:29, David Wei wrote:
> Same as [1] but also with netdev@ as an additional mailing list.
> io_uring zero copy receive is of particular interest to netdev
> participants too, given its tight integration to netdev core.

David, I can guess why you sent it, but it doesn't address the bigger
problem on the networking side. Specifically, why patches were blocked
due to a rule that had not been voiced before and remained blocked even
after pointing this out? And why accusations against me with the same
circumstances, which I equate to defamation, were left as is without
any retraction? To avoid miscommunication, those are questions to Jakub
and specifically about the v3 of the large buffer patchset without
starting a discussion here on later revisions.

Without that cleared, considering that compliance with the new rule
was tried and lead to no results, this behaviour can only be accounted
to malice, and it's hard to see what cooperation is there to be had as
there is no indication Jakub is going to stop maliciously blocking
my work.

In general, if I'm as a patch submitter asked to follow rules, it's
only natural to assume there is a process and rules maintainers keep to
as well. And I'd believe that includes unbiased treatment and technical
merit rather than decision based on mood of the day.

-- 
Pavel Begunkov


  parent reply	other threads:[~2025-10-22 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 20:29 [PATCH 1/1] io_uring zcrx: add MAINTAINERS entry David Wei
2025-10-21 20:49 ` Mina Almasry
2025-10-21 23:39 ` Jakub Kicinski
2025-10-22 11:38 ` Pavel Begunkov [this message]
2025-10-22 13:17   ` Jens Axboe
2025-10-22 14:25     ` Pavel Begunkov
2025-10-22 14:34       ` Jens Axboe
2025-10-22 17:01         ` Pavel Begunkov
2025-10-22 14:30 ` Keith Busch
2025-10-22 14:35   ` Jens Axboe
2025-10-22 17:06 ` Jens Axboe

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=60d18b98-6a25-4db7-a4c6-0c86d6c4f787@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=almasrymina@google.com \
    --cc=dw@davidwei.uk \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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