All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Pal <kuncy7@gmail.com>
To: netdev-bot+sashiko@kernel.org
Cc: Christian Marangi <ansuelsmth@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net: dsa: qca8k: serialize register access
Date: Fri, 23 Oct 2026 13:18:20 +0200	[thread overview]
Message-ID: <20261023111820.10630-1-kuncy7@gmail.com> (raw)
In-Reply-To: <179266392377.3135.12848522239467347386@kernel.org>

Thanks for the review. The issues that exist in released kernels now go
to net as a separate series [1]: the regmap locking from this patch,
with Fixes: c766e077d927; dropping late autocast frames once a request
is over; and a length check on MIB frames.

v3 of the MIB statistics will be rebased on top of them once net-next
reopens, and will address the points raised on 2/2: requests from the
poll and from ethtool sharing req_port and data, 32-bit deltas and
counter resets, the register fallback on link loss, the teardown of
the work, and locking of the raw buffer.

[1] https://lore.kernel.org/netdev/20261022192933.384898-1-kuncy7@gmail.com/

pw-bot: cr

  reply	other threads:[~2026-10-23 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 19:11 [PATCH net-next v2 0/2] net: dsa: qca8k: report port statistics from the MIB Stanislaw Pal
2026-10-19 19:11 ` [PATCH net-next v2 1/2] net: dsa: qca8k: serialize register access Stanislaw Pal
2026-10-22 10:12   ` netdev-bot+sashiko
2026-10-23 11:18     ` Stanislaw Pal [this message]
2026-10-19 19:11 ` [PATCH net-next v2 2/2] net: dsa: qca8k: report port statistics from the MIB Stanislaw Pal
2026-10-22 10:12   ` netdev-bot+sashiko
2026-10-21  1:50 ` [PATCH net-next v2 0/2] " 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=20261023111820.10630-1-kuncy7@gmail.com \
    --to=kuncy7@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.