From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] pinctrl: baytrail: Fix pin being driven low for a while on gpiod_get(..., GPIOD_OUT_HIGH)
Date: Fri, 05 Jun 2020 14:10:54 +0000 [thread overview]
Message-ID: <20200605141054.BC0B120835@mail.kernel.org> (raw)
In-Reply-To: <20200602122130.45630-1-hdegoede@redhat.com>
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.6.15, v5.4.43, v4.19.125, v4.14.182, v4.9.225, v4.4.225.
v5.6.15: Build OK!
v5.4.43: Failed to apply! Possible dependencies:
e2b74419e5cc ("pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output")
v4.19.125: Failed to apply! Possible dependencies:
e2b74419e5cc ("pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output")
v4.14.182: Failed to apply! Possible dependencies:
e2b74419e5cc ("pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output")
v4.9.225: Failed to apply! Possible dependencies:
e2b74419e5cc ("pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output")
v4.4.225: Failed to apply! Possible dependencies:
86e3ef812fe3 ("pinctrl: baytrail: Update gpio chip operations")
bf9a5c96c87c ("pinctrl: baytrail: use gpiochip data pointer")
c501d0b149de ("pinctrl: baytrail: Add pin control operations")
c8f5c4c7c82c ("pinctrl: baytrail: Add pin control data structures")
e2b74419e5cc ("pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-06-05 14:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 12:21 [PATCH] pinctrl: baytrail: Fix pin being driven low for a while on gpiod_get(..., GPIOD_OUT_HIGH) Hans de Goede
2020-06-02 12:21 ` [Intel-gfx] " Hans de Goede
2020-06-02 13:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-06-02 15:23 ` [PATCH] " Andy Shevchenko
2020-06-02 15:23 ` [Intel-gfx] " Andy Shevchenko
2020-06-02 15:25 ` Andy Shevchenko
2020-06-02 15:25 ` [Intel-gfx] " Andy Shevchenko
2020-06-05 14:33 ` Hans de Goede
2020-06-05 14:33 ` [Intel-gfx] " Hans de Goede
2020-06-05 17:09 ` Andy Shevchenko
2020-06-05 17:09 ` [Intel-gfx] " Andy Shevchenko
2020-06-05 17:31 ` Hans de Goede
2020-06-05 17:31 ` [Intel-gfx] " Hans de Goede
2020-06-05 18:45 ` Andy Shevchenko
2020-06-05 18:45 ` [Intel-gfx] " Andy Shevchenko
2020-06-05 14:10 ` Sasha Levin [this message]
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=20200605141054.BC0B120835@mail.kernel.org \
--to=sashal@kernel.org \
--cc=hdegoede@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.