Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	andrew+netdev@lunn.ch, horms@kernel.org,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/4] net: shaper: follow ups to recent fixes
Date: Tue,  9 Jun 2026 11:32:20 -0700	[thread overview]
Message-ID: <20260609183224.1108521-1-kuba@kernel.org> (raw)

As discussed previously on the patch set with real fixes the xa_locking
in shapers is a little confusing, remove it.
Link: https://lore.kernel.org/20260506000628.1501691-2-kuba@kernel.org

The remaining three patches are an attempt to silence AI reviewers,
I believe Sashiko was complaining about these non-issues. Not adding
Reported tags since these are false positives.

Jakub Kicinski (4):
  net: shaper: drop redundant xa_lock() bracketing
  net: shaper: drop unnecessary kfree_rcu in pre_insert
  net: shaper: add a comment why we don't need kfree_rcu() in flush
  net: shaper: add a note that we expect cap dumps to be tiny

 net/shaper/shaper.c | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-06-09 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 18:32 Jakub Kicinski [this message]
2026-06-09 18:32 ` [PATCH net-next 1/4] net: shaper: drop redundant xa_lock() bracketing Jakub Kicinski
2026-06-09 18:32 ` [PATCH net-next 2/4] net: shaper: drop unnecessary kfree_rcu in pre_insert Jakub Kicinski
2026-06-09 18:32 ` [PATCH net-next 3/4] net: shaper: add a comment why we don't need kfree_rcu() in flush Jakub Kicinski
2026-06-09 18:32 ` [PATCH net-next 4/4] net: shaper: add a note that we expect cap dumps to be tiny Jakub Kicinski

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=20260609183224.1108521-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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