From: sashiko-bot@kernel.org
To: a0282524688@gmail.com
Cc: linux-hwmon@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v5 1/7] mfd: nct6694: Move module type macros to shared header
Date: Mon, 25 May 2026 08:25:12 +0000 [thread overview]
Message-ID: <20260525082512.9F61F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260525081736.2904310-2-a0282524688@gmail.com>
> From: Ming Yu <a0282524688@gmail.com>
>
> Move NCT6694_XXX_MOD macro definitions from individual sub-device
> drivers into the shared header include/linux/mfd/nct6694.h.
>
> This is a prerequisite for supporting multiple transport interfaces
> (USB, HIF) without duplicating these 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/20260525081736.2904310-1-a0282524688@gmail.com?part=1
prev parent reply other threads:[~2026-05-25 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260525081736.2904310-1-a0282524688@gmail.com>
2026-05-25 8:17 ` [PATCH v5 1/7] mfd: nct6694: Move module type macros to shared header a0282524688
2026-05-25 8:25 ` 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=20260525082512.9F61F1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=a0282524688@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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