From: Jon Hunter <jonathanh@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>,
Marcel Ziswiler <marcel@ziswiler.com>,
Matthias Reichl <hias@horus.com>
Subject: Re: [PATCH] ASoC: core: Fix deferral of machine drivers
Date: Fri, 11 Jan 2019 08:43:24 +0000 [thread overview]
Message-ID: <96f2e729-8ec2-44ee-448c-255c07c068b9@nvidia.com> (raw)
In-Reply-To: <20190110164835.GF9541@sirena.org.uk>
On 10/01/2019 16:48, Mark Brown wrote:
> On Thu, Jan 10, 2019 at 12:13:36PM +0000, Jon Hunter wrote:
>> On 09/01/2019 18:36, Mark Brown wrote:
>>> On Tue, Jan 08, 2019 at 05:28:14PM +0000, Jon Hunter wrote:
>
>>>> - struct snd_soc_dai_link_component *platform;
>>>> + struct snd_soc_dai_link_component platform;
>
>>> This breaks the build for the SCU cards (and we needs a little rebase
>>> against another fix I just merged, though I did do that when applying).
>
>> Sorry I still don't see the build break, can you point me to it?
>
> I'd need to find your patch again and fix the rebase issue. It was
> assigning a pointer to a platform IIRC.
Sorry I still don't see it. Happen to recall the config you were using
to build? I tried enabling the various SH soundcards (which I believe
the SCU card is under).
Jon
--
nvpublic
next prev parent reply other threads:[~2019-01-11 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 17:28 Jon Hunter
2019-01-09 2:09 ` Kuninori Morimoto
2019-01-09 10:52 ` Jon Hunter
2019-01-09 18:36 ` Mark Brown
2019-01-10 12:13 ` Jon Hunter
2019-01-10 16:48 ` Mark Brown
2019-01-11 8:43 ` Jon Hunter [this message]
2019-01-11 13:23 ` 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=96f2e729-8ec2-44ee-448c-255c07c068b9@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hias@horus.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=marcel@ziswiler.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
all inboxes | Powered by JetHome®