From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: robh@kernel.org, linux-leds@vger.kernel.org,
dmitry.torokhov@gmail.com, conor+dt@kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
lee@kernel.org
Subject: Re: [PATCH v6 6/6 RESEND] mfd: motorola-cpcap: add support for Mot CPCAP composition
Date: Thu, 25 Jun 2026 08:23:36 +0000 [thread overview]
Message-ID: <20260625082336.F08BF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260625081812.33474-7-clamor95@gmail.com>
> Add a MFD subdevice composition used in Tegra20 based Mot board
> (Motorola Atrix 4G and Droid X2).
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260625081812.33474-1-clamor95@gmail.com?part=6
prev parent reply other threads:[~2026-06-25 8:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 8:18 [PATCH v6 0/6 RESEND] mfd: cpcap: convert documentation to schema and add Mot board support Svyatoslav Ryhel
2026-06-25 8:18 ` [PATCH v6 1/6 RESEND] dt-bindings: leds: leds-cpcap: convert to DT schema Svyatoslav Ryhel
2026-06-25 8:24 ` sashiko-bot
2026-06-25 8:18 ` [PATCH v6 2/6 RESEND] dt-bindings: input: cpcap-pwrbutton: " Svyatoslav Ryhel
2026-06-25 8:23 ` sashiko-bot
2026-06-25 8:18 ` [PATCH v6 3/6 RESEND] dt-bindings: mfd: motorola-cpcap: " Svyatoslav Ryhel
2026-06-25 8:18 ` [PATCH v6 4/6 RESEND] dt-bindings: mfd: motorola-cpcap: document Mapphone and Mot CPCAP Svyatoslav Ryhel
2026-06-25 8:27 ` sashiko-bot
2026-06-25 8:18 ` [PATCH v6 5/6 RESEND] mfd: motorola-cpcap: diverge configuration per-board Svyatoslav Ryhel
2026-06-25 8:29 ` sashiko-bot
2026-06-25 8:18 ` [PATCH v6 6/6 RESEND] mfd: motorola-cpcap: add support for Mot CPCAP composition Svyatoslav Ryhel
2026-06-25 8:23 ` 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=20260625082336.F08BF1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@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