mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wentao Liang <vulab@iscas.ac.cn>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Jeff Garzik <jeff@garzik.org>,
	Stephen Hemminger <stephen@networkplumber.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: cxgb: Fix skb reference leak in espibug_workaround_t204()
Date: Sun, 08 Nov 2026 10:34:46 -0000	[thread overview]
Message-ID: <20261108101000.2147805-1-vulab@iscas.ac.cn> (raw)
In-Reply-To: <20260917073655.5d7c9ecb@kernel.org>

Hi Jakub,

I am very sorry for the late reply, and for the flood of patches that
made it necessary. You are right on both points, and I apologize for the
extra work and confusion this caused.

You are right that I sent far more patches at once than anyone could
review, and more than I could follow up on. The hard limit of 15 patches
per person, and the guidance to stay at 8 or fewer when the changes are
of low value, exist so that the feedback on one posting can be applied to
the next. I did not respect that, and that is on me.

I understand why you asked for a one-month pause on new patches from
@iscas.ac.cn for drivers/net and net/. I have also gone back to the
kernel documentation on subsystem identification, patch set organization
and testing, and on how this kind of work should be submitted, and I will
follow it.

To be clear about how these patches are produced: we use static analysis
tools to find candidate issues, and then DeepSeek and GPT-6.1 Sol to
audit the candidates and help prepare the fixes. I review every change
and sign it off myself, and I take responsibility for anything I send.

This has been an important lesson. I am going through the remaining
feedback one item at a time by hand, and replying to each one promptly.
Going forward I will not send patches in bulk, and I will keep every
posting well within what I can review and answer. I have also shared
your message with my colleagues, as you asked.

The cxgb patch is a small reference leak fix in an old T2 driver. A v2
that also covers the single-port timer callback with the same pattern is
ready; I will send it separately as one patch rather than in this reply.
If you would rather I drop it, please tell me and I will.

Sorry again, and thank you for your patience.

Wentao


  reply	other threads:[~2026-11-08 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 10:54 Wentao Liang
2026-09-17 14:36 ` Jakub Kicinski
2026-11-08 10:34   ` Wentao Liang [this message]
2026-11-09 18:41     ` Jakub Kicinski
2026-09-21 11:35 ` 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=20261108101000.2147805-1-vulab@iscas.ac.cn \
    --to=vulab@iscas.ac.cn \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=jeff@garzik.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stephen@networkplumber.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

all inboxes | Powered by JetHome®