[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191009204017.GK22365@dtor-ws>
Date: Wed, 9 Oct 2019 13:40:17 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Andi Shyti <andi@...zian.org>
Cc: Stephan Gerhold <stephan@...hold.net>,
Simon Shields <simon@...eageos.org>,
linux-input@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Input: mms114 - add support for mms345l
On Wed, Oct 09, 2019 at 10:26:12AM +0300, Andi Shyti wrote:
> Hi Dmitry,
>
> > > There was a related patch [2] that removes I2C_M_NOSTART for all models,
> > > but it seems abandoned and I do not have any other model for testing.
> > > Therefore, this patch implements the least instrusive solution
> > > and only removes I2C_M_NOSTART for MMS345L.
> >
> > Hmm, at this point I am inclined to pick up Andi's patch since it seems
> > to work for you and him and it looks like Android drivers are not using
> > I2C_M_NOSTART. I wonder if this was some quirk/big on the platform where
> > it was originally developed.
>
> I completely forgot about that patch :)
>
> I should refresh some old work on that device which was left
> undone.
>
> > Any objections?
>
> It's OK for me. If you can just update my e-mail, please, when
> applying the patch to "andi@...zian.org". Thanks!
Andi, any chance you could resend it with the new email? One thing that
I try to avoid modifying whenever I can is S-O-B strings...
Thanks.
--
Dmitry
Powered by blists - more mailing lists