From: sashiko-bot@kernel.org
To: a0282524688@gmail.com
Cc: "Oliver Hartkopp" <socketcan@hartkopp.net>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
mfd@lists.linux.dev, linux-watchdog@vger.kernel.org,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-hwmon@vger.kernel.org,
"Vincent Mailhol" <mailhol@kernel.org>,
linux-can@vger.kernel.org, linux-rtc@vger.kernel.org,
lee@kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v8 06/13] mfd: nct6694: Move module type macros to shared header
Date: Wed, 07 Oct 2026 09:28:26 +0000 [thread overview]
Message-ID: <sashiko-outbox-162793@kernel.org> (raw)
In-Reply-To: <20261007092102.3768818-7-a0282524688@gmail.com>
> From: Ming Yu <a0282524688@gmail.com>
>
> Each sub-device driver defines the module type used by its own
> commands. The upcoming HIF transport also needs to recognise
> NCT6694_RPT_MOD, as report accesses are served from a separate
> register space rather than through the command mailbox.
>
> Move all module types into the shared header so that the transports
> and the sub-device drivers use a single set of definitions.
>
> No functional change.
>
> Signed-off-by: Ming Yu <a0282524688@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261007092102.3768818-1-a0282524688@gmail.com?part=6
prev parent reply other threads:[~2026-10-07 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261007092102.3768818-1-a0282524688@gmail.com>
2026-10-07 9:20 ` [PATCH v8 06/13] mfd: nct6694: Move module type macros to shared header a0282524688
2026-10-07 9:28 ` sashiko-bot [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=sashiko-outbox-162793@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=a0282524688@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=lee@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=sashiko-reviews@lists.linux.dev \
--cc=socketcan@hartkopp.net \
/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