Linux cryptographic layer development
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <u.kleine-koenig@pengutronix.de>
Cc: <alexandre.belloni@bootlin.com>, <Nicolas.Ferre@microchip.com>,
	<linux-crypto@vger.kernel.org>, <kernel@pengutronix.de>,
	<Claudiu.Beznea@microchip.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-i2c@vger.kernel.org>, <herbert@gondor.apana.org.au>,
	<davem@davemloft.net>
Subject: Re: [PATCH] crypto: atmel-ecc - Remove duplicated error reporting in .remove()
Date: Wed, 8 Jun 2022 08:35:25 +0000	[thread overview]
Message-ID: <87243f0b-8496-bfe1-3d44-81b4405927e9@microchip.com> (raw)
In-Reply-To: <20220608070408.odie7hrcnfasegbr@pengutronix.de>

On 6/8/22 10:04, Uwe Kleine-König wrote:
> Hello
> 

Hi,

> On Wed, Jun 08, 2022 at 04:33:48AM +0000, Tudor.Ambarus@microchip.com wrote:
>> On 5/20/22 20:21, Uwe Kleine-König wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> Returning an error value in an i2c remove callback results in an error
>>> message being emitted by the i2c core, but otherwise it doesn't make a
>>> difference. The device goes away anyhow and the devm cleanups are
>>> called.
>>>
>>> As atmel_ecc_remove() already emits an error message on failure and the
>>> additional error message by the i2c core doesn't add any useful
>>> information, change the return value to zero to suppress this message.
>>>
>>> Also make the error message a bit more drastical because when the device
>>> is still busy on remove, it's likely that it will access freed memory
>>> soon.
>>>
>>> This patch is a preparation for making i2c remove callbacks return void.
>>>
>>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>> Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> In the past patches were picked up by Herbert. I assume your R-b tag was

he still does.

> the missing bit to make him pick up this patch? To make a bit more sure

probably not.

> that will happen, I added him and davem to Cc.

Herbert usually queues patches in a two week time frame. Let's wait for him.

Cheers,
ta

  reply	other threads:[~2022-06-08  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 13:59 Bug in atmel-ecc driver Uwe Kleine-König
2022-05-17 10:24 ` Uwe Kleine-König
2022-05-17 13:11   ` Tudor.Ambarus
2022-05-17 14:33     ` Uwe Kleine-König
2022-05-18 10:07       ` Tudor.Ambarus
2022-05-18 21:36         ` Uwe Kleine-König
2022-05-20 17:21         ` [PATCH] crypto: atmel-ecc - Remove duplicated error reporting in .remove() Uwe Kleine-König
2022-06-07  6:48           ` Uwe Kleine-König
2022-06-08  4:33           ` Tudor.Ambarus
2022-06-08  7:04             ` Uwe Kleine-König
2022-06-08  8:35               ` Tudor.Ambarus [this message]
2022-06-10  9:14           ` Herbert Xu

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=87243f0b-8496-bfe1-3d44-81b4405927e9@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --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