From: Petr Machata <petrm@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>
Cc: Petr Machata <petrm@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
<mlxsw@nvidia.com>
Subject: [PATCH net-next v2 0/3] mlxsw: Improvements
Date: Mon, 8 Jul 2024 16:23:39 +0200 [thread overview]
Message-ID: <cover.1720447210.git.petrm@nvidia.com> (raw)
This patchset contains assortments of improvements to the mlxsw driver.
Please see individual patches for details.
v2:
- Patch #1:
- changed to WARN_ONCE() with some prints
- Patch #2:
- call thermal_cooling_device_unregister() unconditionally and mention
it in the commit message
- Patch #3:
- reword the commit message to reflect the fact that the change both
suppresses a warning and avoid concurrent access
Ido Schimmel (2):
mlxsw: core_thermal: Report valid current state during cooling device
registration
mlxsw: pci: Lock configuration space of upstream bridge during reset
Petr Machata (1):
mlxsw: Warn about invalid accesses to array fields
.../ethernet/mellanox/mlxsw/core_thermal.c | 51 +++++++++----------
drivers/net/ethernet/mellanox/mlxsw/item.h | 4 ++
drivers/net/ethernet/mellanox/mlxsw/pci.c | 6 +++
3 files changed, 35 insertions(+), 26 deletions(-)
--
2.45.0
next reply other threads:[~2024-07-08 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 14:23 Petr Machata [this message]
2024-07-08 14:23 ` [PATCH net-next v2 1/3] mlxsw: Warn about invalid accesses to array fields Petr Machata
2024-07-08 14:23 ` [PATCH net-next v2 2/3] mlxsw: core_thermal: Report valid current state during cooling device registration Petr Machata
2024-07-08 14:23 ` [PATCH net-next v2 3/3] mlxsw: pci: Lock configuration space of upstream bridge during reset Petr Machata
2024-07-09 8:50 ` [PATCH net-next v2 0/3] mlxsw: Improvements Przemek Kitszel
2024-07-10 2:10 ` 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=cover.1720447210.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--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 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.