linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lakshay Piplani <lakshay.piplani@nxp.com>,
	linux-kernel@vger.kernel.org, jdelvare@suse.com,
	linux@roeck-us.net, linux-hwmon@vger.kernel.org, corbet@lwn.net,
	linux-doc@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org
Cc: vikash.bansal@nxp.com, priyanka.jain@nxp.com,
	shashank.rebbapragada@nxp.com
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: (lm75) Add binding for NXP P3T1750
Date: Fri, 25 Jul 2025 12:10:32 +0200	[thread overview]
Message-ID: <81fb59e3-1c62-4b43-bcb4-31af1abd8a15@kernel.org> (raw)
In-Reply-To: <20250725095811.2717763-1-lakshay.piplani@nxp.com>

On 25/07/2025 11:58, Lakshay Piplani wrote:
> Add "nxp,p3t1750" to the lm75 compatible list.
> 
> Signed-off-by: Lakshay Piplani <lakshay.piplani@nxp.com>
> ---
>  Documentation/devicetree/bindings/hwmon/lm75.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/hwmon/lm75.yaml b/Documentation/devicetree/bindings/hwmon/lm75.yaml
> index c38255243f57..d0fa98eb38b1 100644
> --- a/Documentation/devicetree/bindings/hwmon/lm75.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/lm75.yaml
> @@ -29,6 +29,7 @@ properties:
>        - maxim,max31726
>        - maxim,mcp980x
>        - nxp,p3t1755
> +      - nxp,p3t1750

Same comment to NXP as usually. I really wished NXP stopped repeating
the same issues:

Does not look like keeping order.

Best regards,
Krzysztof

      parent reply	other threads:[~2025-07-25 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  9:58 [PATCH 1/2] dt-bindings: hwmon: (lm75) Add binding for NXP P3T1750 Lakshay Piplani
2025-07-25  9:58 ` [PATCH 2/2] hwmon: (lm75) Add NXP P3T1750 support Lakshay Piplani
2025-07-25 10:10 ` Krzysztof Kozlowski [this message]

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=81fb59e3-1c62-4b43-bcb4-31af1abd8a15@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=lakshay.piplani@nxp.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=priyanka.jain@nxp.com \
    --cc=robh@kernel.org \
    --cc=shashank.rebbapragada@nxp.com \
    --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 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).