From: "Heiko Stübner" <heiko@sntech.de>
To: "Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Conor Dooley <conor.dooley@microchip.com>,
linux-pwm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 09/11] pwm: rockchip: Propagate errors in .get_state() to the caller
Date: Wed, 30 Nov 2022 19:37:12 +0100 [thread overview]
Message-ID: <23426970.EfDdHjke4D@diego> (raw)
In-Reply-To: <20221130152148.2769768-10-u.kleine-koenig@pengutronix.de>
Am Mittwoch, 30. November 2022, 16:21:46 CET schrieb Uwe Kleine-König:
> .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>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2022-11-30 18:37 UTC|newest]
Thread overview: 47+ 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 02/11] pwm/tracing: Also record trace events for failed API calls Uwe Kleine-König
2022-11-30 20:15 ` Steven Rostedt
2022-12-01 7:09 ` Uwe Kleine-König
2022-11-30 15:21 ` [PATCH v2 03/11] drm/bridge: ti-sn65dsi86: Propagate errors in .get_state() to the caller Uwe Kleine-König
2022-12-01 15:37 ` Doug Anderson
2022-12-04 21:09 ` Uwe Kleine-König
2022-12-04 21:31 ` Laurent Pinchart
2022-12-05 15:25 ` Doug Anderson
2022-11-30 15:21 ` [PATCH v2 04/11] leds: qcom-lpg: " 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
2022-11-30 15:21 ` [PATCH v2 05/11] pwm: crc: " Uwe Kleine-König
2022-11-30 15:21 ` [PATCH v2 06/11] pwm: cros-ec: " Uwe Kleine-König
2022-12-01 2:41 ` Tzung-Bi Shih
2022-11-30 15:21 ` [PATCH v2 07/11] pwm: imx27: " Uwe Kleine-König
2022-11-30 15:21 ` [PATCH v2 08/11] pwm: mtk-disp: " Uwe Kleine-König
2022-12-01 13:11 ` AngeloGioacchino Del Regno
2022-11-30 15:21 ` [PATCH v2 09/11] pwm: rockchip: " Uwe Kleine-König
2022-11-30 18:37 ` Heiko Stübner [this message]
2022-11-30 15:21 ` [PATCH v2 10/11] pwm: sprd: " Uwe Kleine-König
2022-12-01 1:18 ` Baolin Wang
2022-11-30 15:21 ` [PATCH v2 11/11] pwm: Handle .get_state() failures Uwe Kleine-König
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=23426970.EfDdHjke4D@diego \
--to=heiko@sntech.de \
--cc=conor.dooley@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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