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 0/3] mlxsw: Improvements
Date: Mon, 1 Jul 2024 18:41:52 +0200 [thread overview]
Message-ID: <cover.1719849427.git.petrm@nvidia.com> (raw)
This patchset contains assortments of improvements to the mlxsw driver.
Please see individual patches for details.
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 | 50 ++++++++++---------
drivers/net/ethernet/mellanox/mlxsw/item.h | 2 +
drivers/net/ethernet/mellanox/mlxsw/pci.c | 6 +++
3 files changed, 34 insertions(+), 24 deletions(-)
--
2.45.0
next reply other threads:[~2024-07-01 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 16:41 Petr Machata [this message]
2024-07-01 16:41 ` [PATCH net-next 1/3] mlxsw: Warn about invalid accesses to array fields Petr Machata
2024-07-02 7:08 ` Przemek Kitszel
2024-07-03 12:40 ` Ido Schimmel
2024-07-08 9:45 ` Petr Machata
2024-07-01 16:41 ` [PATCH net-next 2/3] mlxsw: core_thermal: Report valid current state during cooling device registration Petr Machata
2024-07-02 7:27 ` Przemek Kitszel
2024-07-09 16:06 ` Rafael J. Wysocki
2024-07-01 16:41 ` [PATCH net-next 3/3] mlxsw: pci: Lock configuration space of upstream bridge during reset Petr Machata
2024-07-02 7:35 ` Przemek Kitszel
2024-07-03 14:42 ` Ido Schimmel
2024-07-12 21:21 ` Bjorn Helgaas
2024-07-14 11:29 ` Ido Schimmel
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.1719849427.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).