From: "Paul Sajna" <sajattack@postmarketos.org>
To: "David Heidelberg" <david@ixit.cz>, "Lee Jones" <lee@kernel.org>,
"Pavel Machek" <pavel@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nikita Travkin" <nikitos.tr@gmail.com>,
"Alexey Min" <alexeymin@minlexx.ru>,
"Griffin Kroah-Hartman" <griffin@kroah.com>
Cc: "Nikita Travkin" <nikita@trvn.ru>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v5 2/3] leds: aw2013: Add AW2027 support
Date: Thu, 12 Nov 2026 22:20:29 +0000 [thread overview]
Message-ID: <4d30540910d8af03de850769e326906550b15574@postmarketos.org> (raw)
In-Reply-To: <11724004-3e85-4f7f-a683-5ff511863bc6@ixit.cz>
November 12, 2026 at 10:10 PM, "David Heidelberg" <david@ixit.cz mailto:david@ixit.cz?to=%22David%20Heidelberg%22%20%3Cdavid%40ixit.cz%3E > wrote:
> instead of comment (which should be formatted such as /* */), I assume you could use #define here?
I could, but then for completeness I would want to spell out all the aw2013 current levels, which might be too noisy. Or calculate it, which would be hard to read. I think comment is the best for now.
next prev parent reply other threads:[~2026-11-12 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 21:22 [PATCH v5 0/3] " Paul Sajna via B4 Relay
2026-11-12 21:22 ` [PATCH v5 1/3] dt-bindings: leds: aw2013: Add awinic,aw2027 compatible Paul Sajna via B4 Relay
2026-11-12 21:22 ` [PATCH v5 2/3] leds: aw2013: Add AW2027 support Paul Sajna via B4 Relay
2026-11-12 22:10 ` David Heidelberg
2026-11-12 22:20 ` Paul Sajna [this message]
2026-11-12 21:22 ` [PATCH v5 3/3] leds: aw2013: Use dev_err_probe Paul Sajna via B4 Relay
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=4d30540910d8af03de850769e326906550b15574@postmarketos.org \
--to=sajattack@postmarketos.org \
--cc=alexeymin@minlexx.ru \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=griffin@kroah.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=nikitos.tr@gmail.com \
--cc=pavel@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®