From: Guenter Roeck <linux@roeck-us.net>
To: Naresh Solanki <naresh.solanki@9elements.com>,
Jean Delvare <jdelvare@suse.com>
Cc: mazziesaccount@gmail.com,
Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (pmbus/mp2975) Fix IRQ masking
Date: Mon, 4 Mar 2024 09:00:41 -0800 [thread overview]
Message-ID: <3383421b-bda2-48c5-bc49-d3d9f2ecfe25@roeck-us.net> (raw)
In-Reply-To: <20240304164446.4153915-1-naresh.solanki@9elements.com>
On 3/4/24 08:44, Naresh Solanki wrote:
> From: Patrick Rudolph <patrick.rudolph@9elements.com>
>
> The MP2971/MP2973 use a custom 16bit register format for
> SMBALERT_MASK which doesn't follow the PMBUS specification.
>
> Map the PMBUS defined bits used by the common code onto the custom
> format used by MPS and since the SMBALERT_MASK is currently never read
> by common code only implement the mapping for write transactions.
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
> ---
What will it take for people to start providing change logs ?
Why is that do difficult, and why do people seem to assume that
I have the time to look up old e-mail chains ?
I'll have to write some boilerplate reply. Until I get to do that,
I'll simply ignore patches without change logs (which I will do
once I have the boilerplate as well, only then it will look nicer).
Guenter
next prev parent reply other threads:[~2024-03-04 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 16:44 [PATCH v2] hwmon: (pmbus/mp2975) Fix IRQ masking Naresh Solanki
2024-03-04 17:00 ` Guenter Roeck [this message]
2024-03-05 10:14 ` 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=3383421b-bda2-48c5-bc49-d3d9f2ecfe25@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.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