linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH stable 5.2/4.19] Revert "Input: elantech - enable SMBus on new (2018+) systems"
Date: Fri, 6 Sep 2019 11:53:47 +0200	[thread overview]
Message-ID: <20190906095347.GC16843@kroah.com> (raw)
In-Reply-To: <20190906085345.26279-1-benjamin.tissoires@redhat.com>

On Fri, Sep 06, 2019 at 10:53:45AM +0200, Benjamin Tissoires wrote:
> This reverts commit 60956b018bfe23b879405a7d88103d0a8f06a5e3.
> 
> This patch depends on an other series:
> https://patchwork.kernel.org/project/linux-input/list/?series=122327&state=%2A&archive=both
> 
> It was a mistake to backport it in the v5.2 branch, as there
> is a high chance we encounter a touchpad that needs the series
> above.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=204733
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=204771
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> 
> ---
> 
> Hi,
> 
> this is a stable only patch aimed at kernels v5.2 and v4.19 branches.
> 
> We already have 2 bug reports of a failing touchpad, and I don't think
> it is worth trying to get a smoother touchpad if we randomly
> break a few of them in the way.

Now reverted, I'll push out some new releases with that now so people's
machines get back to a working state.

thanks,

greg k-h

      reply	other threads:[~2019-09-06  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  8:53 [PATCH stable 5.2/4.19] Revert "Input: elantech - enable SMBus on new (2018+) systems" Benjamin Tissoires
2019-09-06  9:53 ` Greg Kroah-Hartman [this message]

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=20190906095347.GC16843@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.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).