From: Hans de Goede <hdegoede@redhat.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>,
	Jiri Kosina <jikos@kernel.org>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] HID: i2c-hid: Silently fail probe for CHPN0001 touchscreen
Date: Sat, 7 Apr 2018 11:42:03 +0200	[thread overview]
Message-ID: <585b5f34-8b00-bf84-5b99-fa204a3e3e75@redhat.com> (raw)
In-Reply-To: <MW2PR2101MB1034700D2EE61E78EA6C13E7FBBA0@MW2PR2101MB1034.namprd21.prod.outlook.com>
Hi,
On 06-04-18 22:05, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed by the -stable helper bot and determined
> to be a high probability candidate for -stable trees. (score: 20.8863)
> 
> The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126.
> 
> v4.16: Build OK!
> v4.15.15: Build OK!
> v4.14.32: Build OK!
> v4.9.92: Failed to apply! Possible dependencies:
>      94116f8126de ("ACPI: Switch to use generic guid_t in acpi_evaluate_dsm()")
> 
> v4.4.126: Failed to apply! Possible dependencies:
>      94116f8126de ("ACPI: Switch to use generic guid_t in acpi_evaluate_dsm()")
Cool, first time I see this bot in action, nice work.
> Please let us know if you'd like to have this patch included in a stable tree.
So FWIW this commit is NOT stable material (it cannot hurt, but it is not
necessary). This commit really only makes sense together with a new touchscreen
driver which does actually know how to handle the CHPN0001 touchscreen.
For future mails like this, do I understand the mail correctly that if I
do NOT want a patch picked up by the -stable helper bot to go to stable
I do not have to do anything?
Regards,
Hans
next prev parent reply	other threads:[~2018-04-07  9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180403131634.13187-2-hdegoede@redhat.com>
2018-04-06 20:05 ` [PATCH 2/2] HID: i2c-hid: Silently fail probe for CHPN0001 touchscreen Sasha Levin
2018-04-07  9:42   ` Hans de Goede [this message]
2018-04-09 17:07     ` Sasha Levin
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=585b5f34-8b00-bf84-5b99-fa204a3e3e75@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=Alexander.Levin@microsoft.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@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).