From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bard liao <yung-chuan.liao@linux.intel.com>
Subject: Re: linux-next: build warnings after merge of the sound-asoc-fixes tree
Date: Fri, 21 Aug 2020 09:25:53 -0500 [thread overview]
Message-ID: <a982589b-9bc1-6439-99de-3ce6efdab469@linux.intel.com> (raw)
In-Reply-To: <20200821110117.GC4870@sirena.org.uk>
On 8/21/20 6:01 AM, Mark Brown wrote:
> On Thu, Aug 20, 2020 at 07:01:15PM -0500, Pierre-Louis Bossart wrote:
>
>> There is a companion patch 1eb629363aa35 ("ASoC: SOF: Intel: hda: import
>> SOUNDWIRE_INIT namespace") that does the import, not sure what causes the
>> warning?
>
> A patch which was not sent as part of the same series and where no
> dependency was mentioned :(
yes, sorry about that, i just noticed the two patches were sent one
after the other but without the dependency.
Do you have a means to fix this on your side or do you need Bard/I to
resend it?
next prev parent reply other threads:[~2020-08-21 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 23:39 linux-next: build warnings after merge of the sound-asoc-fixes tree Stephen Rothwell
2020-08-21 0:01 ` Pierre-Louis Bossart
2020-08-21 0:37 ` Stephen Rothwell
2020-08-21 11:01 ` Mark Brown
2020-08-21 14:25 ` Pierre-Louis Bossart [this message]
2020-08-21 14:48 ` Mark Brown
2020-08-21 15:18 ` Pierre-Louis Bossart
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=a982589b-9bc1-6439-99de-3ce6efdab469@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yung-chuan.liao@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