From: Guenter Roeck <linux@roeck-us.net>
To: Zac Lanzon <lanzonza@gmail.com>, linux-hwmon@vger.kernel.org
Cc: Aleksa Savic <savicaleksa83@gmail.com>,
Edward Blair <edward.blair@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] hwmon: (asus_rog_ryujin) Fix pump control source on the Ryujin III
Date: Fri, 30 Oct 2026 10:56:56 -0700 [thread overview]
Message-ID: <a1a0582a-271e-44b8-a1ff-2e657e20b33a@roeck-us.net> (raw)
In-Reply-To: <CAPusjWrmKH4wHK6LY7NFi1=+rzDY0uq5N4dgKC4FuUh_=xGhLg@mail.gmail.com>
On 10/30/26 10:38, Zac Lanzon wrote:
> Hi Guenter,
>
> Gentle ping on v2 of this series. Patch 1 fixes the pump control
> source on the Ryujin III and is Cc'd to stable. Patch 2 adds
> pwm1_enable.
>
> I can rebase onto hwmon-next and resend if that helps.
>
The patches are queued, and I'll push them into my published hwmon-next
branch after the commit window closes. The first one should actually
already be visible in the hwmon branch since it is a bug fix.
I did send a note, but I am having trouble with gmail; it often refuses
to accept my e-mails, claiming that I am a Spammer. Since I am working
for Google, I guess they must know ;-).
Guenter
next prev parent reply other threads:[~2026-10-30 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 11:41 [PATCH v2 0/2] hwmon: (asus_rog_ryujin) Ryujin III pump control source Zac Lanzon
2026-09-28 11:41 ` [PATCH v2 1/2] hwmon: (asus_rog_ryujin) Fix pump control source on the Ryujin III Zac Lanzon
2026-10-26 20:52 ` Guenter Roeck
2026-10-30 17:38 ` Zac Lanzon
2026-10-30 17:56 ` Guenter Roeck [this message]
2026-09-28 11:41 ` [PATCH v2 2/2] hwmon: (asus_rog_ryujin) Add pwm1_enable for the Ryujin III pump Zac Lanzon
2026-10-26 20:53 ` Guenter Roeck
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=a1a0582a-271e-44b8-a1ff-2e657e20b33a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=edward.blair@gmail.com \
--cc=lanzonza@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=savicaleksa83@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®