From: Dmitry Osipenko <digetx@gmail.com>
To: Stefan Agner <stefan@agner.ch>, thierry.reding@gmail.com
Cc: airlied@linux.ie, jonathanh@nvidia.com,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/tegra: return with probe defer if GPIO subsystem is not ready
Date: Fri, 26 Jul 2019 17:46:14 +0300 [thread overview]
Message-ID: <f035a8ba-ffa7-b98b-a444-db8b4bbd34ec@gmail.com> (raw)
In-Reply-To: <cd14bca0a1f1e097265602a1d5f0c0f5@agner.ch>
26.07.2019 17:23, Stefan Agner пишет:
> Hi Thierry, Hi Dave,
>
> On 2018-09-07 01:31, Stefan Agner wrote:
>> On 26.07.2018 06:36, Stefan Agner wrote:
>>> If the GPIO subsystem is not ready make sure to return -EPROBE_DEFER
>>> instead of silently continuing without HPD.
>>>
>>> Reported-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>>
>> I think this did not get merged yet, any chance to get it in?
>
> Any chance to get this in in the next merge window?
The patch isn't relevant anymore (since v5.3) because the code was
changed and now propagates the proper error code in a case of error,
please see [1].
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.3-rc1&id=bbad640709fd43ff77b8838c409c977c0b28430c
next prev parent reply other threads:[~2019-07-26 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 13:36 [PATCH] drm/tegra: return with probe defer if GPIO subsystem is not ready Stefan Agner
2018-09-06 23:31 ` Stefan Agner
2019-07-26 14:23 ` Stefan Agner
2019-07-26 14:46 ` Dmitry Osipenko [this message]
2019-07-26 14:57 ` Stefan Agner
2019-07-26 15:00 ` Dmitry Osipenko
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=f035a8ba-ffa7-b98b-a444-db8b4bbd34ec@gmail.com \
--to=digetx@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stefan@agner.ch \
--cc=thierry.reding@gmail.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 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).