All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	kernel@pengutronix.de, linux-media@vger.kernel.org
Subject: Re: [PATCH] media: i2c: dw9714: Return zero in remove callback
Date: Tue, 26 Apr 2022 11:02:55 +0200	[thread overview]
Message-ID: <20220426090255.nhguw7nd4asxrhab@pengutronix.de> (raw)
In-Reply-To: <Ymeq5Q4kVu1yoKFq@paasikivi.fi.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]

On Tue, Apr 26, 2022 at 11:18:45AM +0300, Sakari Ailus wrote:
> Hi Uwe,
> 
> On Mon, Apr 25, 2022 at 09:13:45PM +0200, Uwe Kleine-König wrote:
> > Hello,
> > 
> > On Thu, Mar 31, 2022 at 03:31:32PM +0200, Uwe Kleine-König wrote:
> > > The only effect of returning an error code in an i2c remove callback is
> > > that the i2c core emits a generic warning and still removes the device.
> > > 
> > > So even if disabling the regulator fails it's sensible to further cleanup
> > > and then return zero to only emit a single error message.
> > > 
> > > This patch is a preparation for making i2c remove callbacks return void.
> > > 
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > ---
> > >  drivers/media/i2c/dw9714.c | 1 -
> > >  1 file changed, 1 deletion(-)
> > > 
> > > diff --git a/drivers/media/i2c/dw9714.c b/drivers/media/i2c/dw9714.c
> > > index cd7008ad8f2f..982ed8afebf5 100644
> > > --- a/drivers/media/i2c/dw9714.c
> > > +++ b/drivers/media/i2c/dw9714.c
> > > @@ -201,7 +201,6 @@ static int dw9714_remove(struct i2c_client *client)
> > >  		if (ret) {
> > >  			dev_err(&client->dev,
> > >  				"Failed to disable vcc: %d\n", ret);
> > > -			return ret;
> > >  		}
> > >  	}
> > >  	pm_runtime_set_suspended(&client->dev);
> > 
> > Who cares for this driver and so for this patch?
> 
> I do.
> 
> The patch is in the media stage tree now (you should have received an
> e-mail about it) from where it eventually gets to the media tree.

Ah I did. I wasn't aware of it, because the mail doesn't have the
in-reply-to header set such that my MUA doesn't sort it to the patch
mail.

I saw this mail now. Let me note that it's intransparent for me how your
Sob line was added to the patch. The mail says the patch was queued,
does that mean it's about to be applied and will appear in next soon? Or
is it only queued to be looked at? (I assume the former.)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

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

  reply	other threads:[~2022-04-26  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 13:31 [PATCH] media: i2c: dw9714: Return zero in remove callback Uwe Kleine-König
2022-04-25 19:13 ` Uwe Kleine-König
2022-04-26  8:18   ` Sakari Ailus
2022-04-26  9:02     ` Uwe Kleine-König [this message]
2022-04-27  6:15       ` Sakari Ailus

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=20220426090255.nhguw7nd4asxrhab@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=kernel@pengutronix.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.