[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191013213950.GB16344@jack.zhora.eu>
Date: Mon, 14 Oct 2019 00:39:50 +0300
From: Andi Shyti <andi@...zian.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Andi Shyti <andi@...zian.org>,
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
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...
sure, I will resend the patches, but it might take some time (a
few days I hope) because I don't have the devices with me right
now for testing (and I added some small fixes, as well)
Thanks,
Andi
Powered by blists - more mailing lists