stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gerecke <killertofu@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Jason Gerecke <jason.gerecke@wacom.com>,
	Linux Input <linux-input@vger.kernel.org>,
	Ping Cheng <pinglinux@gmail.com>,
	"# v3.17+" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] HID: wacom: Don't set tool type until we're in range
Date: Thu, 25 Apr 2019 10:47:42 -0700	[thread overview]
Message-ID: <CANRwn3QVG2XBr-h53kimQkQ0W=KOuTxHppzTLcS=i7CFiqC_bA@mail.gmail.com> (raw)
In-Reply-To: <20190425121505.3AD33218AD@mail.kernel.org>

I can produce a version of this patch specific to v4.14.113. Please
let me know the proper process for submitting such a patch.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....


On Thu, Apr 25, 2019 at 5:15 AM Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: a48324de6d4d HID: wacom: Bluetooth IRQ for Intuos Pro should handle prox/range.
>
> The bot has tested the following trees: v5.0.9, v4.19.36, v4.14.113.
>
> v5.0.9: Build OK!
> v4.19.36: Build OK!
> v4.14.113: Failed to apply! Possible dependencies:
>     Unable to calculate
>
>
> How should we proceed with this patch?
>
> --
> Thanks,
> Sasha

  parent reply	other threads:[~2019-04-25 17:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 22:12 [PATCH 1/2] HID: wacom: Don't set tool type until we're in range Gerecke, Jason
2019-04-24 22:12 ` [PATCH 2/2] HID: wacom: Don't report anything prior to the tool entering range Gerecke, Jason
     [not found]   ` <20190425121506.7EBEC218B0@mail.kernel.org>
2019-04-25 17:47     ` Jason Gerecke
2019-04-26 16:35       ` Gerecke, Jason
2019-06-11 19:02         ` Jason Gerecke
2019-06-11 19:22           ` Greg KH
2019-06-11 20:45             ` Jason Gerecke
2019-06-12  7:10               ` Greg KH
2019-06-15 15:32                 ` Greg KH
     [not found] ` <20190425121505.3AD33218AD@mail.kernel.org>
2019-04-25 17:47   ` Jason Gerecke [this message]
2019-04-26  3:33     ` [PATCH 1/2] HID: wacom: Don't set tool type until we're in range Sasha Levin
2019-04-26 16:34       ` Gerecke, Jason
2019-05-07 18:43 ` Jason Gerecke
2019-05-17 14:27 ` Benjamin Tissoires

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='CANRwn3QVG2XBr-h53kimQkQ0W=KOuTxHppzTLcS=i7CFiqC_bA@mail.gmail.com' \
    --to=killertofu@gmail.com \
    --cc=jason.gerecke@wacom.com \
    --cc=linux-input@vger.kernel.org \
    --cc=pinglinux@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).