From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>,
Mac Chiang <mac.chiang@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: Build failure after merge of the sound-current
Date: Tue, 17 Sep 2019 22:56:00 +0200 [thread overview]
Message-ID: <s5h8sqmtzfj.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190917195722.GG3524@sirena.co.uk>
On Tue, 17 Sep 2019 21:57:23 +0200,
Mark Brown wrote:
>
> On Tue, Sep 17, 2019 at 11:38:58AM +0100, Mark Brown wrote:
>
> > IIRC there was some previous discussion of a dependency on other changes
> > here but I thought that was resolved? I've reverted that commit for
> > today.
>
> This wasn't resolved, Stephen's been carrying a patch for it in -next.
> I didn't see this mentioned in the pull request for sound to Linus...
> might be an issue if it gets pulled before tip.
Hm, strange, I couldn't get the warning when I tested allyesconfig on
the tree merged onto 5.3...
Takashi
next prev parent reply other threads:[~2019-09-17 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 10:38 Build failure after merge of the sound-current Mark Brown
2019-09-17 19:57 ` Mark Brown
2019-09-17 20:56 ` Takashi Iwai [this message]
2019-09-17 20:56 ` [alsa-devel] " Pierre-Louis Bossart
2019-09-17 21:02 ` Takashi Iwai
2019-09-17 21:09 ` 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=s5h8sqmtzfj.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mac.chiang@intel.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.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