From: Lee Jones <lee@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Pavel Machek <pavel@ucw.cz>,
Thierry Reding <thierry.reding@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>,
Bjorn Andersson <andersson@kernel.org>,
Satya Priya <quic_c_skakit@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-leds@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH v2 04/11] leds: qcom-lpg: Propagate errors in .get_state() to the caller
Date: Thu, 5 Jan 2023 16:29:28 +0000 [thread overview]
Message-ID: <Y7b66AKdRzqoRYst@google.com> (raw)
In-Reply-To: <20230105135438.j7fdocows5pmtwyr@pengutronix.de>
On Thu, 05 Jan 2023, Uwe Kleine-König wrote:
> On Wed, Jan 04, 2023 at 04:56:21PM +0000, Lee Jones wrote:
> > On Mon, 05 Dec 2022, Pavel Machek wrote:
> >
> > > Hi!
> > >
> > > > .get_state() can return an error indication. Make use of it to propagate
> > > > failing hardware accesses.
> > > >
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > >
> > > Acked-by: Pavel Machek <pavel@ucw.cz>
> >
> > What's the merge strategy for this? Can it go in on its own?
>
> It's already in Linus's tree as fea768cf68c04d68ea2a8091c559667378f3b77c.
Interesting. All good then, thanks for letting me know.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-01-05 16:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 15:21 [PATCH v2 00/11] pwm: Allow .get_state to fail Uwe Kleine-König
2022-11-30 15:21 ` [PATCH v2 01/11] pwm: Make .get_state() callback return an error code Uwe Kleine-König
2022-12-01 1:17 ` Baolin Wang
2022-12-01 2:41 ` Tzung-Bi Shih
2022-12-01 8:03 ` Neil Armstrong
2022-12-01 9:30 ` nobuhiro1.iwamatsu
2022-12-01 10:22 ` Andre Przywara
2022-12-01 13:16 ` Uwe Kleine-König
2022-12-01 14:17 ` Andre Przywara
2022-12-01 10:43 ` Dave Stevenson
2022-12-01 15:37 ` Doug Anderson
2022-12-05 20:50 ` Jernej Škrabec
2022-12-05 22:30 ` Pavel Machek
2022-11-30 15:21 ` [PATCH v2 04/11] leds: qcom-lpg: Propagate errors in .get_state() to the caller Uwe Kleine-König
2022-12-04 21:04 ` Uwe Kleine-König
2022-12-04 22:28 ` Pavel Machek
2022-12-05 22:31 ` Pavel Machek
2023-01-04 16:56 ` Lee Jones
2023-01-05 13:54 ` Uwe Kleine-König
2023-01-05 16:29 ` Lee Jones [this message]
2022-12-01 11:11 ` [PATCH v2 00/11] pwm: Allow .get_state to fail Conor Dooley
2022-12-01 13:19 ` Uwe Kleine-König
2022-12-01 13:28 ` Conor Dooley
2022-12-09 21:47 ` Andy Shevchenko
2022-12-10 9:18 ` Uwe Kleine-König
2022-12-10 20:57 ` Andy Shevchenko
2022-12-10 22:41 ` Uwe Kleine-König
2022-12-11 13:31 ` Andy Shevchenko
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=Y7b66AKdRzqoRYst@google.com \
--to=lee@kernel.org \
--cc=andersson@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=pavel@ucw.cz \
--cc=quic_c_skakit@quicinc.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).