From: Lee Jones <lee@kernel.org>
To: Lakshay Piplani <lakshay.piplani@nxp.com>
Cc: linux-kernel@vger.kernel.org, linux-i3c@lists.infradead.org,
alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
broonie@kernel.org, Frank.Li@nxp.com, lgirdwood@gmail.com,
vikash.bansal@nxp.com, priyanka.jain@nxp.com,
aman.kumarpandey@nxp.com
Subject: Re: [PATCH v6 7/7] i3c: hub: p3h2x4x: Add support for NXP P3H2x4x I3C hub functionality
Date: Tue, 10 Mar 2026 09:07:03 +0000 [thread overview]
Message-ID: <20260310090703.GB183676@google.com> (raw)
In-Reply-To: <20260310065727.3759342-7-lakshay.piplani@nxp.com>
On Tue, 10 Mar 2026, Lakshay Piplani wrote:
> From: Aman Kumar Pandey <aman.kumarpandey@nxp.com>
>
> Add I3C hub functionality for the NXP P3H2x4x family of multiport hubs.
> These devices support downstream target ports that can be configured
> as I3C, I2C, or SMBus.
>
> This driver enables:
> - I3C/I2C communication between host and hub
> - Transparent communication with downstream devices
> - Target port configuration (I3C/I2C/SMBus)
> - MCTP device support
> - In-band interrupt handling
>
> P3H2440/P3H2441 support 4 target ports.
> P3H2840/P3H2841 support 8 target ports.
>
> Signed-off-by: Aman Kumar Pandey <aman.kumarpandey@nxp.com>
> Signed-off-by: Vikash Bansal <vikash.bansal@nxp.com>
> Signed-off-by: Lakshay Piplani <lakshay.piplani@nxp.com>
Where is your cover letter?
Why did I have to scour 7 patches just to find out that there is nothing
for me to do and that I shouldn't have been sent the set in the first
place?
Please provide cover letters for large sets like this.
--
Lee Jones [李琼斯]
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: Lakshay Piplani <lakshay.piplani@nxp.com>
Cc: linux-kernel@vger.kernel.org, linux-i3c@lists.infradead.org,
alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
broonie@kernel.org, Frank.Li@nxp.com, lgirdwood@gmail.com,
vikash.bansal@nxp.com, priyanka.jain@nxp.com,
aman.kumarpandey@nxp.com
Subject: Re: [PATCH v6 7/7] i3c: hub: p3h2x4x: Add support for NXP P3H2x4x I3C hub functionality
Date: Tue, 10 Mar 2026 09:07:03 +0000 [thread overview]
Message-ID: <20260310090703.GB183676@google.com> (raw)
In-Reply-To: <20260310065727.3759342-7-lakshay.piplani@nxp.com>
On Tue, 10 Mar 2026, Lakshay Piplani wrote:
> From: Aman Kumar Pandey <aman.kumarpandey@nxp.com>
>
> Add I3C hub functionality for the NXP P3H2x4x family of multiport hubs.
> These devices support downstream target ports that can be configured
> as I3C, I2C, or SMBus.
>
> This driver enables:
> - I3C/I2C communication between host and hub
> - Transparent communication with downstream devices
> - Target port configuration (I3C/I2C/SMBus)
> - MCTP device support
> - In-band interrupt handling
>
> P3H2440/P3H2441 support 4 target ports.
> P3H2840/P3H2841 support 8 target ports.
>
> Signed-off-by: Aman Kumar Pandey <aman.kumarpandey@nxp.com>
> Signed-off-by: Vikash Bansal <vikash.bansal@nxp.com>
> Signed-off-by: Lakshay Piplani <lakshay.piplani@nxp.com>
Where is your cover letter?
Why did I have to scour 7 patches just to find out that there is nothing
for me to do and that I shouldn't have been sent the set in the first
place?
Please provide cover letters for large sets like this.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-03-10 9:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 6:57 [PATCH v6 1/7] i3c: master: Expose the APIs to support I3C hub Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-10 6:57 ` [PATCH v6 2/7] i3c: master: Add " Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-10 16:50 ` Frank Li
2026-03-10 16:50 ` Frank Li
2026-03-10 6:57 ` [PATCH v6 3/7] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-11 6:13 ` Krzysztof Kozlowski
2026-03-11 6:13 ` Krzysztof Kozlowski
2026-03-13 11:09 ` [EXT] " Lakshay Piplani
2026-03-13 11:09 ` Lakshay Piplani
2026-03-13 16:01 ` Krzysztof Kozlowski
2026-03-13 16:01 ` Krzysztof Kozlowski
2026-03-17 11:34 ` Lakshay Piplani
2026-03-17 11:34 ` Lakshay Piplani
2026-03-17 11:39 ` Krzysztof Kozlowski
2026-03-17 11:39 ` Krzysztof Kozlowski
2026-03-10 6:57 ` [PATCH v6 4/7] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-10 9:08 ` Jorge Marques
2026-03-10 9:08 ` Jorge Marques
2026-03-10 16:57 ` Frank Li
2026-03-10 16:57 ` Frank Li
2026-03-10 6:57 ` [PATCH v6 5/7] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-10 17:00 ` Frank Li
2026-03-10 17:00 ` Frank Li
2026-03-10 6:57 ` [PATCH v6 6/7] i3c: hub: Add support for the I3C interface in the I3C hub Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-10 9:11 ` Jorge Marques
2026-03-10 9:11 ` Jorge Marques
2026-03-10 9:25 ` Jorge Marques
2026-03-10 9:25 ` Jorge Marques
2026-03-10 20:21 ` kernel test robot
2026-03-10 20:21 ` kernel test robot
2026-03-11 0:59 ` kernel test robot
2026-03-11 0:59 ` kernel test robot
2026-03-10 6:57 ` [PATCH v6 7/7] i3c: hub: p3h2x4x: Add support for NXP P3H2x4x I3C hub functionality Lakshay Piplani
2026-03-10 6:57 ` Lakshay Piplani
2026-03-10 9:07 ` Lee Jones [this message]
2026-03-10 9:07 ` Lee Jones
2026-03-10 18:28 ` Frank Li
2026-03-10 18:28 ` Frank Li
2026-03-10 22:10 ` kernel test robot
2026-03-10 22:10 ` kernel test robot
2026-03-10 23:26 ` kernel test robot
2026-03-10 23:26 ` kernel test robot
2026-03-10 14:40 ` [PATCH v6 1/7] i3c: master: Expose the APIs to support I3C hub kernel test robot
2026-03-10 14:40 ` kernel test robot
2026-03-10 16:46 ` Frank Li
2026-03-10 16:46 ` Frank Li
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=20260310090703.GB183676@google.com \
--to=lee@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=aman.kumarpandey@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lakshay.piplani@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=priyanka.jain@nxp.com \
--cc=robh@kernel.org \
--cc=vikash.bansal@nxp.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.