From: Lee Jones <lee.jones@linaro.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: linux-pwm@vger.kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com, Linux-imx@nxp.com,
kernel@pengutronix.de, u.kleine-koenig@pengutronix.de,
festevam@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 2/3] pwm: imx27: Use dev_err_probe() to simplify error handling
Date: Tue, 11 Aug 2020 07:37:19 +0100 [thread overview]
Message-ID: <20200811063719.GE4411@dell> (raw)
In-Reply-To: <1597127072-26365-2-git-send-email-Anson.Huang@nxp.com>
On Tue, 11 Aug 2020, Anson Huang wrote:
> dev_err_probe() can reduce code size, uniform error handling and record the
> defer probe reason etc., use it to simplify the code.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> changes since V1:
> - remove redundant return value print.
> ---
> drivers/pwm/pwm-imx27.c | 25 ++++++-------------------
> 1 file changed, 6 insertions(+), 19 deletions(-)
Acked-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-11 6:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 6:24 [PATCH V2 1/3] pwm: imx-tpm: Use dev_err_probe() to simplify error handling Anson Huang
2020-08-11 6:24 ` [PATCH V2 2/3] pwm: imx27: " Anson Huang
2020-08-11 6:37 ` Lee Jones [this message]
2020-08-11 7:00 ` Uwe Kleine-König
2020-08-11 6:24 ` [PATCH V2 3/3] pwm: imx1: " Anson Huang
2020-08-11 6:37 ` Lee Jones
2020-08-11 6:58 ` Uwe Kleine-König
2020-08-11 6:37 ` [PATCH V2 1/3] pwm: imx-tpm: " Lee Jones
2020-08-11 7:00 ` Uwe Kleine-König
2020-09-17 6:37 ` Anson Huang
2020-11-11 18:05 ` Thierry Reding
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=20200811063719.GE4411@dell \
--to=lee.jones@linaro.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).