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: Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
"Vadim Pasternak" <vadimp@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/3] mlxsw: Provide enhancements and new feature
Date: Fri, 22 Sep 2023 19:18:35 +0200 [thread overview]
Message-ID: <cover.1695396848.git.petrm@nvidia.com> (raw)
Vadim Pasternak writes:
Patch #1 - Optimize transaction size for efficient retrieval of module
data.
Patch #3 - Enable thermal zone binding with new cooling device.
Patch #4 - Employ standard macros for dividing buffer into the chunks.
Vadim Pasternak (3):
mlxsw: reg: Limit MTBR register payload to a single data record
mlxsw: core: Extend allowed list of external cooling devices for
thermal zone binding
mlxsw: i2c: Utilize standard macros for dividing buffer into chunks
drivers/net/ethernet/mellanox/mlxsw/core_env.c | 2 +-
drivers/net/ethernet/mellanox/mlxsw/core_hwmon.c | 2 +-
drivers/net/ethernet/mellanox/mlxsw/core_thermal.c | 1 +
drivers/net/ethernet/mellanox/mlxsw/i2c.c | 4 +---
drivers/net/ethernet/mellanox/mlxsw/reg.h | 6 +++---
5 files changed, 7 insertions(+), 8 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-22 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 17:18 Petr Machata [this message]
2023-09-22 17:18 ` [PATCH net-next 1/3] mlxsw: reg: Limit MTBR register payload to a single data record Petr Machata
2023-09-22 17:18 ` [PATCH net-next 2/3] mlxsw: core: Extend allowed list of external cooling devices for thermal zone binding Petr Machata
2023-09-22 17:18 ` [PATCH net-next 3/3] mlxsw: i2c: Utilize standard macros for dividing buffer into chunks Petr Machata
2023-09-28 12:42 ` [PATCH net-next 0/3] mlxsw: Provide enhancements and new feature Simon Horman
2023-10-02 7: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.1695396848.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 \
--cc=vadimp@nvidia.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.