Re: [PATCH v3 0/7] Additional fixes for Azoteq IQS7222A/B/C

[Jeff LaBundy <jeff@labundy.com>]

Hi Dmitry,

On Fri, Oct 28, 2022 at 09:14:54AM -0700, Dmitry Torokhov wrote:
> On Fri, Oct 28, 2022 at 08:25:07AM -0500, Jeff LaBundy wrote:
> > Hi Mattijs,
> > 
> > Thank you for reaching out and helping to review this series.
> > 
> > On Fri, Oct 28, 2022 at 09:56:37AM +0200, Mattijs Korpershoek wrote:
> > > On sam., oct. 22, 2022 at 19:54, Jeff LaBundy <jeff@labundy.com> wrote:
> > > 
> > > > This series comprises a second round of fixes that result from
> > > > continued testing and updated guidance from the vendor.
> > > >
> > > > Jeff LaBundy (7):
> > > >   Input: iqs7222 - drop unused device node references
> > > >   dt-bindings: input: iqs7222: Reduce 'linux,code' to optional
> > > >   Input: iqs7222 - report malformed properties
> > > >   dt-bindings: input: iqs7222: Correct minimum slider size
> > > >   Input: iqs7222 - protect against undefined slider size
> > > >   dt-bindings: input: iqs7222: Add support for IQS7222A v1.13+
> > > >   Input: iqs7222 - add support for IQS7222A v1.13+
> > > >
> > > >  .../bindings/input/azoteq,iqs7222.yaml        |  25 +-
> > > >  drivers/input/misc/iqs7222.c                  | 504 +++++++++++-------
> > > >  2 files changed, 311 insertions(+), 218 deletions(-)
> > > 
> > > Not sure this requires a re-send, but the series seems ill-formatted.
> > > all patches are posted separately to the list instead of replying to the
> > > cover letter. Is that expected?
> > 
> > Yes, this was a goof on my part. I see that the series is threaded
> > properly on Patchwork but not on lore.kernel.org.
> > 
> > Much to my dismay, my mail service recently began enforcing OAuth2
> > but declined to enable app-specific passwords as Gmail and others
> > do. I can therefore no longer use git send-email directly and I am
> 
> You can teach git to work with OAuth - I am using Gmail without
> application specific passwords. You simply need to use the credential
> helper that would give the token instead of a password.
> 
> I have the following in my .gitconfig:
> 
> [credential]
> 	helper = cache --timeout=3000
> 	helper = local-helper
> 
> and I am using the attached script that gets client ID and refresh token
> from the disk and generates authentication token. The script is using
> Google OAUTH library and endpoint, but since you taught mutt how to work
> with your provider you should be able to adjust it as needed.
> 
> And please do not judge me for this script ;)

Thank you for these clues; I will give this method a shot.

> 
> > instead emulating it with a script that tunnels patches through mutt.
> > 
> > In this last series, my script inadvertenly dropped the '< >' from
> > the cover letter's message ID, so some mailers may see this series
> > as seven separate threads. This is fixed now.
> > 
> > That being said, I see this series was already applied earlier this
> > week; I think a mail simply did not go out. So no further action is
> > needed.
> 
> Sorry, my bad, I forgot to send the notice.
> 
> Thanks.
> 
> -- 
> Dmitry

Kind regards,
Jeff LaBundy