From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jose Ramon San Buenaventura <jose.sanbuenaventura@analog.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-i2c@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com>
Subject: Re: [PATCH v2 0/2] Add adm1281 support
Date: Mon, 22 Apr 2024 05:28:43 +0200 [thread overview]
Message-ID: <9b95f926-b96c-4266-b292-3c3cd362905e@kernel.org> (raw)
In-Reply-To: <20240422025123.29770-1-jose.sanbuenaventura@analog.com>
On 22/04/2024 04:51, Jose Ramon San Buenaventura wrote:
> This patch removes the extra case added in the adm1275_read_byte_data
> for STATUS_CML reads. Upon checking, the reads for the STATUS_CML register
> is already handled in the pmbus_core.
>
> It was also clarified and agreed upon that any other actionable steps
> involving the STATUS_CML error flags should be added in the pmbus_core
> and not on the specific chip driver.
>
Where is the changelog? It's v2, so what happened here?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-22 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 2:51 [PATCH v2 0/2] Add adm1281 support Jose Ramon San Buenaventura
2024-04-22 2:51 ` [PATCH v2 1/2] dt-bindings: hwmon: adm1275: add adm1281 Jose Ramon San Buenaventura
2024-04-22 2:51 ` [PATCH v2 2/2] hwmon: pmbus: adm1275: add adm1281 support Jose Ramon San Buenaventura
2024-04-22 7:20 ` Nuno Sá
2024-04-22 3:28 ` Krzysztof Kozlowski [this message]
2024-04-22 3:45 ` [PATCH v2 0/2] Add " Guenter Roeck
2024-04-22 4:09 ` SanBuenaventura, Jose
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=9b95f926-b96c-4266-b292-3c3cd362905e@kernel.org \
--to=krzk@kernel.org \
--cc=Delphine_CC_Chiu@Wiwynn.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=jose.sanbuenaventura@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).