From: Lee Jones <lee@kernel.org>
To: Paul Sajna <sajattack@postmarketos.org>
Cc: sashiko-reviews@lists.linux.dev, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 5/6] leds: aw2013: Prevent writes to unpowered chip
Date: Wed, 21 Oct 2026 10:41:18 +0100 [thread overview]
Message-ID: <20261021094118.GF1795367@google.com> (raw)
In-Reply-To: <338bdb9dddd9cf502a05ae8a79ccf5bb368b37a7@postmarketos.org>
On Tue, 20 Oct 2026, Paul Sajna wrote:
> October 20, 2026 at 3:16 AM, "Lee Jones" <lee@kernel.org mailto:lee@kernel.org?to=%22Lee%20Jones%22%20%3Clee%40kernel.org%3E > wrote:
>
> > >
> > No more reviews until Sashko is clean or everything has been reasoned about.
>
>
> Thanks for the review, wasn't expecting anything until I fixed Sashiko, just didn't have time to circle back yet.
Totally understandable.
A very short note to that effect would save us all a great deal of time.
--
Lee Jones
next prev parent reply other threads:[~2026-10-21 9:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 5:39 [PATCH v3 0/6] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-13 5:39 ` [PATCH v3 1/6] dt-bindings: leds: aw2013: Add awinic,aw2027 compatible Paul Sajna
2026-10-13 5:43 ` sashiko-bot
2026-10-13 6:31 ` Krzysztof Kozlowski
2026-10-13 5:39 ` [PATCH v3 2/6] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-13 5:53 ` sashiko-bot
2026-10-20 10:16 ` Lee Jones
2026-10-13 5:39 ` [PATCH v3 3/6] leds: aw2013: Use dev_err_probe Paul Sajna
2026-10-13 5:52 ` sashiko-bot
2026-10-13 5:39 ` [PATCH v3 4/6] leds: aw2013: Move assignment of chip->num_leds Paul Sajna
2026-10-13 5:57 ` sashiko-bot
2026-10-13 5:39 ` [PATCH v3 5/6] leds: aw2013: Prevent writes to unpowered chip Paul Sajna
2026-10-13 5:53 ` sashiko-bot
2026-10-20 10:16 ` Lee Jones
2026-10-20 19:28 ` Paul Sajna
2026-10-21 9:41 ` Lee Jones [this message]
2026-10-13 5:40 ` [PATCH v3 6/6] leds: aw2013: Move reset register write Paul Sajna
2026-10-13 5:46 ` sashiko-bot
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=20261021094118.GF1795367@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sajattack@postmarketos.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