From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vadim Pasternak <vadimp@nvidia.com>,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH platform-next 06/11] platform/mellanox: mlxreg-dpu: Add initial support for Nvidia DPU
Date: Sat, 11 Jan 2025 09:40:34 +0100 [thread overview]
Message-ID: <7f65cf30-e5fc-445e-80e3-034b6d85de3d@kernel.org> (raw)
In-Reply-To: <20250110134515.8164-7-vadimp@nvidia.com>
On 10/01/2025 14:45, Vadim Pasternak wrote:
> Provide platform support for Nvidia (DPU) Data Processor Unit for the
> Smart Switch SN4280.
>
> The Smart Switch equipped with:
> - Nvidia COME module based on AMD EPYC™ Embedded 3451 CPU.
> - Nvidia Spectrum-3 ASIC.
> - Four DPUs, each equipped with Nvidia BF3 ARM based processor and
> with Lattice LFD2NX-40 FPGA device.
> - 28xQSFP-DD external ports.
> - Two power supplies.
> - Four cooling drawers.
>
> Drivers provides support for the platform management and monitoring
> of DPU components.
> It includes support for health events, resets and boot progress
> indications logic, implemented by FPGA device.
>
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
> Reviewed-by: Ciju Rajan K <crajank@nvidia.com>
Why the review is after your SoB? This was never done on the lists
right? So first you received review internally and then sent a patch,
You also need to Cc people whose tags you include. Please use standard
tools for sending patches like git send-email or b4, which do it
automatically.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-11 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 13:44 [PATCH platform-next 00/11] platform/mellanox: Add support for new systems, amendments, relocate mlx-platform module Vadim Pasternak
2025-01-10 13:44 ` [PATCH platform-next 01/11] mellanox: Relocate mlx-platform driver Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 02/11] platform: mellanox: mlx-platform: Cosmetic changes Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 03/11] platform: mellanox: mlx-platform: Change register name Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 04/11] platform_data/mlxreg: Add capability bit and mask fields Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 05/11] platform/mellanox: mlxreg-hotplug: Add support for new flavor of capability registers Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 06/11] platform/mellanox: mlxreg-dpu: Add initial support for Nvidia DPU Vadim Pasternak
2025-01-11 8:40 ` Krzysztof Kozlowski [this message]
2025-01-10 13:45 ` [PATCH platform-next 07/11] platform: mellanox: Introduce support of Nvidia smart switch Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 08/11] platform: mellanox: mlx-platform: Add support for new Nvidia system Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 09/11] platform: mellanox: nvsw-sn2200: Add support for new system flavour Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 10/11] Documentation/ABI: Add new attribute for mlxreg-io sysfs interfaces Vadim Pasternak
2025-01-10 13:45 ` [PATCH platform-next 11/11] MAINTAINERS: Remove MELLANOX PLATFORM DRIVER item Vadim Pasternak
2025-01-11 8:38 ` Krzysztof Kozlowski
2025-01-11 9:17 ` Vadim Pasternak
2025-01-11 9:21 ` Krzysztof Kozlowski
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=7f65cf30-e5fc-445e-80e3-034b6d85de3d@kernel.org \
--to=krzk@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--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.