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.7, v5.4.35, v4.19.118, v4.14.177, v4.9.220, v4.4.220.
v5.6.7: Build OK!
v5.4.35: Build OK!
v4.19.118: Build OK!
v4.14.177: Build OK!
v4.9.220: Failed to apply! Possible dependencies:
a0b028597d59 ("pinctrl: cherryview: Add support for GMMR GPIO opregion")
v4.4.220: Build OK!
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
Re: [PATCH] pinctrl: cherryview: Ensure _REG(ACPI_ADR_SPACE_GPIO, 1) gets called
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] pinctrl: cherryview: Ensure _REG(ACPI_ADR_SPACE_GPIO, 1) gets called
- From: Sasha Levin <sashal@xxxxxxxxxx>
- Date: Fri, 01 May 2020 02:55:24 +0000
- In-reply-to: <20200429104651.63643-1-hdegoede@redhat.com>
- References: <20200429104651.63643-1-hdegoede@redhat.com>
- References:
- [PATCH] pinctrl: cherryview: Ensure _REG(ACPI_ADR_SPACE_GPIO, 1) gets called
- From: Hans de Goede
- [PATCH] pinctrl: cherryview: Ensure _REG(ACPI_ADR_SPACE_GPIO, 1) gets called
- Prev by Date: Re: [PATCH v3 4/4] gpio: xilinx: Utilize for_each_set_clump macro
- Next by Date: [PATCH] pinctrl: qcom: Add affinity callbacks to msmgpio IRQ chip
- Previous by thread: Re: [PATCH] pinctrl: cherryview: Ensure _REG(ACPI_ADR_SPACE_GPIO, 1) gets called
- Next by thread: linusw/for-next build: 6 builds: 0 failed, 6 passed, 44 warnings (v5.7-rc2-34-g9e581cd14663)
- Index(es):
 |