From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
vkoul@kernel.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH 0/2] soundwire: Kconfig/build improvements
Date: Mon, 14 Oct 2019 10:59:54 -0500 [thread overview]
Message-ID: <779f012b-4994-09c5-5944-164cd053a724@linux.intel.com> (raw)
In-Reply-To: <20190916185739.32184-1-pierre-louis.bossart@linux.intel.com>
On 9/16/19 1:57 PM, Pierre-Louis Bossart wrote:
> The Intel kbuild test reported issues with COMPILE_TEST or
> cross-compilation when SOF is enabled, fix. This has no functional
> impact.
Vinod, if you are back at your desk, those patches are almost a month
old. thanks!
>
> Pierre-Louis Bossart (2):
> soundwire: intel: add missing headers for cross-compilation
> soundwire: intel: remove X86 dependency
>
> drivers/soundwire/Kconfig | 2 +-
> drivers/soundwire/intel.c | 1 +
> drivers/soundwire/intel_init.c | 1 +
> 3 files changed, 3 insertions(+), 1 deletion(-)
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-14 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 18:57 [alsa-devel] [PATCH 0/2] soundwire: Kconfig/build improvements Pierre-Louis Bossart
2019-09-16 18:57 ` [alsa-devel] [PATCH 1/2] soundwire: intel: add missing headers for cross-compilation Pierre-Louis Bossart
2019-09-16 18:57 ` [alsa-devel] [PATCH 2/2] soundwire: intel: remove X86 dependency Pierre-Louis Bossart
2019-10-14 15:59 ` Pierre-Louis Bossart [this message]
2019-10-16 5:06 ` [alsa-devel] [PATCH 0/2] soundwire: Kconfig/build improvements Vinod Koul
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=779f012b-4994-09c5-5944-164cd053a724@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--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