linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: wsa@kernel.org
Cc: Jeffrey Lin <jeffrey@icurse.nl>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Register lis3lv02d I2C device on Dell Latitude 5480
Date: Mon, 31 Aug 2020 10:13:41 +0200	[thread overview]
Message-ID: <20200831101341.476ce06f@endymion> (raw)
In-Reply-To: <20200805093347.GM1229@kunai>

Hi Wolfram,

On Wed, 05 Aug 2020 11:33:47 +0200, wsa@kernel.org wrote:
> On Tue, Jun 16, 2020 at 07:41:30PM -0400, Jeffrey Lin wrote:
> > Value of /sys/devices/platform/lis3lv02d/position when
> >     Horizontal:     (36,-108,-1152)
> >     Left elevated:  (-432,-126,-1062)
> >     Front elevated: (36,594,-936)
> >     Upside down:    (-126,-252,1098)
> > 
> > Signed-off-by: Jeffrey Lin <jeffrey@icurse.nl>  
> 
> Jean?
> 
> > ---
> >  drivers/i2c/busses/i2c-i801.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
> > index fea644921a76..d7c802e20ae6 100644
> > --- a/drivers/i2c/busses/i2c-i801.c
> > +++ b/drivers/i2c/busses/i2c-i801.c
> > @@ -1268,6 +1268,7 @@ static const struct {
> >  	/*
> >  	 * Additional individual entries were added after verification.
> >  	 */
> > +	{ "Latitude 5480",      0x29 },
> >  	{ "Vostro V131",        0x1d },
> >  };
> >  

No actual code change and not something I can test, so pretty much any
kernel developer is as qualified as I am to deal with it. But yes, OK,
I'm listed as the maintainer for this driver, so I should have replied
earlier, sorry.

Reviewed-by: Jean Delvare <jdelvare@suse.de>

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2020-08-31  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 23:41 [PATCH] i2c: i801: Register lis3lv02d I2C device on Dell Latitude 5480 Jeffrey Lin
2020-08-05  9:33 ` wsa
2020-08-31  8:13   ` Jean Delvare [this message]
2020-09-02  4:51 ` [PATCH v2] " Jeffrey Lin
2020-09-09  8:29   ` Wolfram Sang

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=20200831101341.476ce06f@endymion \
    --to=jdelvare@suse.de \
    --cc=jeffrey@icurse.nl \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@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;
as well as URLs for NNTP newsgroup(s).