public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: florian.fainelli@broadcom.com, rjui@broadcom.com,
	sbranden@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
	yangyicong@hisilicon.com, aisheng.dong@nxp.com,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	kblaiech@nvidia.com, asmaa@nvidia.com, loic.poulain@linaro.org,
	rfoss@kernel.org, ardb@kernel.org, gcherian@marvell.com,
	Liao Chang <liaochang1@huawei.com>,
	linux-i2c@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 0/9] Use dev_err_probe in i2c probe function
Date: Mon, 14 Aug 2023 17:16:31 +0200	[thread overview]
Message-ID: <ZNpFT18MJh2cyEZY@shikoro> (raw)
In-Reply-To: <169165547667.2480436.2965071341321476080.b4-ty@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]

On Thu, Aug 10, 2023 at 10:19:35AM +0200, Andi Shyti wrote:
> Hi
> 
> On Tue, 08 Aug 2023 09:29:45 +0800, Liao Chang wrote:
> > Use the dev_err_probe function instead of dev_err in the probe function
> > so that the printed messge includes the return value and also handles
> > -EPROBE_DEFER nicely.
> > 
> > NOTICE: dev_err_probe always print the second parameter that happens to
> > be the return value, hence the return errno will be removed from the
> > third parameter to avoid a redundant error message.
> > 
> > [...]

Applied to for-next (via Andi's branch), thanks!


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-08-14 15:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  1:29 [PATCH v3 0/9] Use dev_err_probe in i2c probe function Liao Chang
2023-08-08  1:29 ` [PATCH v3 1/9] i2c: bcm2835: Use dev_err_probe in " Liao Chang
2023-08-08  9:37   ` Markus Elfring
2023-08-08 11:31     ` Andi Shyti
2023-08-08  1:29 ` [PATCH v3 2/9] i2c: mlxbf: " Liao Chang
2023-08-08  8:36   ` Krzysztof Kozlowski
2023-08-08 11:29     ` Andi Shyti
2023-08-08 11:31       ` Krzysztof Kozlowski
2023-08-08 11:47         ` Andi Shyti
2023-08-08 15:55           ` Krzysztof Kozlowski
2023-08-09  8:02             ` Andi Shyti
2023-08-08 10:32   ` Markus Elfring
2023-08-08  1:29 ` [PATCH v3 3/9] i2c: xlp9xx: " Liao Chang
2023-08-08  8:36   ` Krzysztof Kozlowski
2023-08-08  1:29 ` [PATCH v3 4/9] i2c: hisi: " Liao Chang
2023-08-08  8:36   ` Krzysztof Kozlowski
2023-08-08  1:29 ` [PATCH v3 5/9] i2c: qcom-cci: " Liao Chang
2023-08-10 15:06   ` Bjorn Andersson
2023-08-08  1:29 ` [PATCH v3 6/9] i2c: pxa: " Liao Chang
2023-08-08  1:29 ` [PATCH v3 7/9] i2c: dln2: " Liao Chang
2023-08-08  1:29 ` [PATCH v3 8/9] i2c: imx-lpi2c: " Liao Chang
2023-08-08  8:37   ` Krzysztof Kozlowski
2023-08-08  1:29 ` [PATCH v3 9/9] i2c: synquacer: " Liao Chang
2023-08-08  8:37   ` Krzysztof Kozlowski
2023-08-09 19:21   ` Andi Shyti
2023-08-10  2:33     ` Liao, Chang
2023-08-10  8:10       ` Andi Shyti
2023-08-10  8:19 ` [PATCH v3 0/9] Use dev_err_probe in i2c " Andi Shyti
2023-08-14 15:16   ` Wolfram Sang [this message]

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=ZNpFT18MJh2cyEZY@shikoro \
    --to=wsa@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=andi.shyti@kernel.org \
    --cc=ardb@kernel.org \
    --cc=asmaa@nvidia.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=festevam@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=gcherian@marvell.com \
    --cc=kblaiech@nvidia.com \
    --cc=kernel@pengutronix.de \
    --cc=liaochang1@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=loic.poulain@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=rjui@broadcom.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sbranden@broadcom.com \
    --cc=shawnguo@kernel.org \
    --cc=yangyicong@hisilicon.com \
    /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