From: Sasha Levin <sashal@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-gpio@vger.kernel.org, kernel@pengutronix.de,
stable@vger.kernel.org
Subject: Re: [PATCH stable (4.4 + 4.9)] gpio: fix oops resulting from calling of_get_named_gpio(NULL, ...)
Date: Fri, 14 Aug 2020 12:29:55 -0400 [thread overview]
Message-ID: <20200814162955.GQ2975990@sasha-vm> (raw)
In-Reply-To: <20200814074711.14044-1-u.kleine-koenig@pengutronix.de>
On Fri, Aug 14, 2020 at 09:47:11AM +0200, Uwe Kleine-König wrote:
>This happens for the spi-imx driver when running a dt-enabled kernel on
>a non-dt machine on Linux 4.0. Among the still supported stable versions
>only 4.4 and 4.9 are affected. (However the spi-imx driver doesn't call
>of_get_named_gpio() since v4.8-rc1 (commit b36581df7e78 ("spi: imx:
>Using existing properties for chipselects")) any more, but the problem
>might still affect other users of of_get_named_gpio().)
>
>In 4.14-rc1 this problem is gone with
>commit 7eb6ce2f2723 ("gpio: Convert to using %pOF instead of
>full_name"). This commit however doesn't seem sensible to backport as it
>depends on ce4fecf1fe15 ("vsprintf: Add %p extension "%pOF" for device
>tree") which doesn't trivially apply to v4.4.
Queued up for 4.9 and 4.4, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2020-08-14 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 7:47 [PATCH stable (4.4 + 4.9)] gpio: fix oops resulting from calling of_get_named_gpio(NULL, ...) Uwe Kleine-König
2020-08-14 16:29 ` 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=20200814162955.GQ2975990@sasha-vm \
--to=sashal@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).