On Sat, Apr 07, 2018 at 11:42:03AM +0200, Hans de Goede wrote:

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.

I'll leave it out, thanks!

...

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?

I would probably try and pick it up without an ack. If possible, even a brief "no" reply if you don't want it in stable would be great. Thanks!