From: Greg KH <gregkh@linuxfoundation.org>
To: Vasyl Vavrychuk <vasyl.vavrychuk@opensynergy.com>
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
stable@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Mathias Crombez <mathias.crombez@faurecia.com>
Subject: Re: [PATCH RESEND v2] virtio-input: add multi-touch support
Date: Wed, 9 Dec 2020 08:01:41 +0100 [thread overview]
Message-ID: <X9B2VRdXgwjxU15J@kroah.com> (raw)
In-Reply-To: <20201208210150.20001-1-vasyl.vavrychuk@opensynergy.com>
On Tue, Dec 08, 2020 at 11:01:50PM +0200, Vasyl Vavrychuk wrote:
> From: Mathias Crombez <mathias.crombez@faurecia.com>
>
> Without multi-touch slots allocated, ABS_MT_SLOT events will be lost by
> input_handle_abs_event.
>
> Signed-off-by: Mathias Crombez <mathias.crombez@faurecia.com>
> Signed-off-by: Vasyl Vavrychuk <vasyl.vavrychuk@opensynergy.com>
> Tested-by: Vasyl Vavrychuk <vasyl.vavrychuk@opensynergy.com>
> ---
> v2: fix patch corrupted by corporate email server
>
> drivers/virtio/Kconfig | 11 +++++++++++
> drivers/virtio/virtio_input.c | 8 ++++++++
> 2 files changed, 19 insertions(+)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2020-12-09 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 21:01 [PATCH RESEND v2] virtio-input: add multi-touch support Vasyl Vavrychuk
2020-12-08 22:05 ` Dmitry Torokhov
2020-12-18 23:20 ` Vasyl Vavrychuk
2020-12-09 7:01 ` Greg KH [this message]
2020-12-09 8:28 ` Michael S. Tsirkin
2020-12-18 23:25 ` Vasyl Vavrychuk
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=X9B2VRdXgwjxU15J@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.crombez@faurecia.com \
--cc=mst@redhat.com \
--cc=rydberg@bitmath.org \
--cc=stable@vger.kernel.org \
--cc=vasyl.vavrychuk@opensynergy.com \
--cc=virtualization@lists.linux-foundation.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).