From: Thomas Backlund <tmb@mageia.org>
To: Greg KH <gregkh@linuxfoundation.org>, James Feeney <james@nurealm.net>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Sasha Levin <sashal@kernel.org>, Jiri Kosina <jikos@kernel.org>,
<linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] HID: input: make sure the wheel high resolution multiplier is set
Date: Sat, 15 Jun 2019 12:03:04 +0300 [thread overview]
Message-ID: <e158e981-47e6-a7f8-6416-4eff7af2c5d0@mageia.org> (raw)
In-Reply-To: <20190615055019.GC23883@kroah.com>
Den 15-06-2019 kl. 08:50, skrev Greg KH:
> On Fri, Jun 14, 2019 at 04:09:35PM -0600, James Feeney wrote:
>> Hey Everyone
>>
>> On 4/24/19 10:41 AM, Benjamin Tissoires wrote:
>>>>> For a patch to be picked up by stable, it first needs to go in Linus'
>>>>> tree. Currently we are working on 5.1, so any stable patches need to
>>>>> go in 5.1 first. Then, once they hit Linus' tree, the stable team will
>>>>> pick them and backport them in the appropriate stable tree.
>>
>> Hmm - so, I just booted linux 5.1.9, and this patch set is *still* missing from the kernel.
>>
>> Is there anything that we can do about this?
>
> What is the git commit id of the patch in Linus's tree?
>
> As I said before, it can not be backported until it shows up there
> first.
>
That would be:
d43c17ead879ba7c076dc2f5fd80cd76047c9ff4
and
39b3c3a5fbc5d744114e497d35bf0c12f798c134
--
Thomas
next prev parent reply other threads:[~2019-06-15 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:46 Benjamin Tissoires
2019-04-23 15:46 ` [PATCH 2/2] HID: input: fix assignment of .value Benjamin Tissoires
[not found] ` <20190423172117.CC66520835@mail.kernel.org>
2019-04-23 17:54 ` James Feeney
2019-04-23 19:36 ` Sasha Levin
2019-04-24 13:30 ` [PATCH 1/2] HID: input: make sure the wheel high resolution multiplier is set Benjamin Tissoires
2019-04-24 15:42 ` James Feeney
2019-04-24 16:41 ` Benjamin Tissoires
2019-06-14 22:09 ` James Feeney
2019-06-15 5:50 ` Greg KH
2019-06-15 9:03 ` Thomas Backlund [this message]
2019-06-15 15:29 ` Greg KH
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=e158e981-47e6-a7f8-6416-4eff7af2c5d0@mageia.org \
--to=tmb@mageia.org \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=james@nurealm.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=sashal@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
all inboxes | Powered by JetHome®