From: Jon Hunter <jonathanh@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Curtis Malainey <cujomalainey@google.com>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] ASoC: soc-core: Fix probe deferral following prelink failure
Date: Tue, 2 Apr 2019 10:44:34 +0100 [thread overview]
Message-ID: <3053ef10-ba36-ee88-4ca0-d1e39c0ea25c@nvidia.com> (raw)
In-Reply-To: <20190402093159.GF2059@sirena.org.uk>
On 02/04/2019 10:31, Mark Brown wrote:
> On Tue, Apr 02, 2019 at 10:30:34AM +0100, Jon Hunter wrote:
>> On 02/04/2019 10:19, Mark Brown wrote:
>
>>> Oh, if I've applied that's why I don't have it any more. Indeed it's
>>> applied in my 5.1 branch so I don't know what you're expecting here?
>
>> Well I still don't see it in the mainline branch and some boards are
>> still failing to register soundcards with v5.1-rc3 because this is
>> missing. So I am wondering what has happened to the change. It seems it
>> has been dropped.
>
> You can check to see what's in my tree by looking at it directly or at
> -next.
Right I see it in -next. Sorry but what I am asking is if you are
planning to send as a fix for v5.1? Maybe you have not sent out the
fixes yet for v5.1 and so wanted to check.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2019-04-02 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 13:31 [PATCH] ASoC: soc-core: Fix probe deferral following prelink failure Jon Hunter
2019-03-04 15:32 ` Applied "ASoC: soc-core: Fix probe deferral following prelink failure" to the asoc tree Mark Brown
2019-04-01 12:22 ` [PATCH] ASoC: soc-core: Fix probe deferral following prelink failure Jon Hunter
2019-04-02 4:35 ` Mark Brown
2019-04-02 8:52 ` Jon Hunter
2019-04-02 9:19 ` Mark Brown
2019-04-02 9:30 ` Jon Hunter
2019-04-02 9:31 ` Mark Brown
2019-04-02 9:44 ` Jon Hunter [this message]
2019-04-03 3:47 ` Mark Brown
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=3053ef10-ba36-ee88-4ca0-d1e39c0ea25c@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
/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