public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: rn5t618: cleanup i2c_device_id
Date: Thu, 30 Jan 2020 15:24:28 +0000	[thread overview]
Message-ID: <20200130152428.GD3548@dell> (raw)
In-Reply-To: <20200128194555.324cff21@kemnade.info>

On Tue, 28 Jan 2020, Andreas Kemnade wrote:

> Hi,
> 
> just re-checking the patch again. Seems that I have added it on top of my RTC
> series. It breaks because of...
> 
> On Wed, 11 Dec 2019 22:57:31 +0100
> Andreas Kemnade <andreas@kemnade.info> wrote:
> 
> > That list was just empty, so it can be removed if .probe_new
> > instead of .probe is used
> > 
> > Suggested-by: Lee Jones <lee.jones@linaro.org>
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > ---
> >  drivers/mfd/rn5t618.c | 11 ++---------
> >  1 file changed, 2 insertions(+), 9 deletions(-)
> > 
> > diff --git a/drivers/mfd/rn5t618.c b/drivers/mfd/rn5t618.c
> > index 18d56a732b20..70d52b46ee8a 100644
> > --- a/drivers/mfd/rn5t618.c
> > +++ b/drivers/mfd/rn5t618.c
> > @@ -150,8 +150,7 @@ static const struct of_device_id rn5t618_of_match[] = {
> >  };
> >  MODULE_DEVICE_TABLE(of, rn5t618_of_match);
> >  
> > -static int rn5t618_i2c_probe(struct i2c_client *i2c,
> > -			     const struct i2c_device_id *id)
> > +static int rn5t618_i2c_probe(struct i2c_client *i2c)
> >  {
> >  	const struct of_device_id *of_id;
> >  	struct rn5t618 *priv;
> > @@ -251,11 +250,6 @@ static int __maybe_unused rn5t618_i2c_resume(struct device *dev)
> >  	return 0;
> >  }
> >  
> I added the pm stuff above ...
> 
> 
> > -static const struct i2c_device_id rn5t618_i2c_id[] = {
> > -	{ }
> > -};
> > -MODULE_DEVICE_TABLE(i2c, rn5t618_i2c_id);
> > -
> 
> and below it in my RTC series.
> 
> >  static SIMPLE_DEV_PM_OPS(rn5t618_i2c_dev_pm_ops,
> >  			rn5t618_i2c_suspend,
> >  			rn5t618_i2c_resume);
> 
> Do you want to have it rebased so it can be applied first?
> Sorry for the confusion here.

You may as well wait until -rc1 is out and rebase on top of that.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2020-01-30 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 21:57 [PATCH] mfd: rn5t618: cleanup i2c_device_id Andreas Kemnade
2020-01-28 18:45 ` Andreas Kemnade
2020-01-30 15:24   ` Lee Jones [this message]
2020-02-11 22:21     ` Andreas Kemnade

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=20200130152428.GD3548@dell \
    --to=lee.jones@linaro.org \
    --cc=andreas@kemnade.info \
    --cc=linux-kernel@vger.kernel.org \
    /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