From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>,
Naresh Solanki <naresh.solanki@9elements.com>,
Jean Delvare <jdelvare@suse.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sylvester Bauer <sylv@sylv.io>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: hwmon: pmbus: pli209bc: Add bindings
Date: Tue, 15 Oct 2024 16:49:02 +0200 [thread overview]
Message-ID: <b981df66-2501-40ad-8064-158cf93407f7@kernel.org> (raw)
In-Reply-To: <30089bac-e764-45ca-b0fd-f0eb0333e632@roeck-us.net>
On 15/10/2024 16:10, Guenter Roeck wrote:
> On 10/15/24 04:48, Krzysztof Kozlowski wrote:
>> On 15/10/2024 13:33, Naresh Solanki wrote:
>>> Add bindings for Vicor pli1209bc.
>>> It a Digital Supervisor with Isolation for use with BCM Bus Converter
>>> Modules.
>>>
>>> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
>>> ---
>>> .../bindings/hwmon/pmbus/vicor,pli1209bc.yaml | 65 +++++++++++++++++++
>>
>> This has to be squashed with previous patch.
>>
>
> Neither me nor the hwmon mailing list was copied on that previous patch
> (or on an intro patch if there was one), so I have no idea what this
> is about.
Heh... that's even worse because without that visibility you would pick
up this patch only leading to duplicated compatibles warnings.
Naresh, sending such patchsets is really not correct. Be sure you
organize them logically and in fully bisectable way, and then you CC
relevant people.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-15 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 11:33 [PATCH 1/2] dt-bindings: trivial-devices: Remove vicor,pli1209bc Naresh Solanki
2024-10-15 11:33 ` [PATCH 2/2] dt-bindings: hwmon: pmbus: pli209bc: Add bindings Naresh Solanki
2024-10-15 11:48 ` Krzysztof Kozlowski
2024-10-15 14:10 ` Guenter Roeck
2024-10-15 14:49 ` Krzysztof Kozlowski [this message]
2024-10-16 9:50 ` Naresh Solanki
2024-10-16 10:20 ` Naresh Solanki
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=b981df66-2501-40ad-8064-158cf93407f7@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=robh@kernel.org \
--cc=sylv@sylv.io \
/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).