linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 'Dmitry Torokhov' <dmitry.torokhov@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: jingle <jingle.wu@emc.com.tw>,
	kernel@pengutronix.de, linux-input@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: elan_i2c: failed to read report data: -71
Date: Wed, 3 Mar 2021 17:53:37 -0800	[thread overview]
Message-ID: <YEA9oajb7qj6LGPD@google.com> (raw)
In-Reply-To: <20210303200330.udsge64hxlrdkbwt@pengutronix.de>

Hi Uwe,

On Wed, Mar 03, 2021 at 09:03:30PM +0100, Uwe Kleine-König wrote:
> Hello Dmitry,
> 
> On Wed, Mar 03, 2021 at 07:32:23PM +0100, Uwe Kleine-König wrote:
> > Hello,
> > 
> > On Wed, Mar 03, 2021 at 11:13:21AM +0800, jingle wrote:
> > > HI uwe:
> > > 
> > > Please updates this patchs.
> > > 
> > > https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?h=next&id=056115daede8d01f71732bc7d778fb85acee8eb6
> > > 
> > > https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?h=next&id=e4c9062717feda88900b566463228d1c4910af6d
> > 
> > The first was one of the two patches I already tried, but the latter
> > indeed fixes my problem \o/.
> > 
> > @Dmitry: If you don't consider your tree stable, feel free to add a
> > 
> > 	Tested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > 
> > to e4c9062717feda88900b566463228d1c4910af6d.
> 
> Do you consider this patch for stable? I'd like to see it in Debian's
> 5.10 kernel and I guess I'm not the only one who would benefit from such
> a backport.

When I was applying the patches I did not realize that there was already
hardware in the wild that needed it. The patches are now in mainline, so
I can no longer adjust the tags, but I will not object if you propose
them for stable.

Thanks.

-- 
Dmitry

  reply	other threads:[~2021-03-04  1:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 21:09 elan_i2c: failed to read report data: -71 Uwe Kleine-König
2021-03-03  1:26 ` Dmitry Torokhov
2021-03-03 10:41   ` Nikolai Kostrigin
2021-03-03  3:13 ` jingle
2021-03-03 18:32   ` Uwe Kleine-König
2021-03-03 20:03     ` Uwe Kleine-König
2021-03-04  1:53       ` 'Dmitry Torokhov' [this message]
2021-03-04  6:59         ` Uwe Kleine-König
2021-03-04  8:49           ` Nikolai Kostrigin
2021-03-04 13:38             ` Greg KH
2021-03-05 19:18             ` Uwe Kleine-König
2021-03-04 13:38           ` Greg KH
2021-03-26  9:00   ` Egor Ignatov

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=YEA9oajb7qj6LGPD@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=jingle.wu@emc.com.tw \
    --cc=kernel@pengutronix.de \
    --cc=linux-input@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).