From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
liam.r.girdwood@linux.intel.com, jank@cadence.com,
joe@perches.com, srinivas.kandagatla@linaro.org
Subject: Re: [PATCH 0/2] soundwire: fix Kconfig select/depend issues
Date: Sun, 14 Apr 2019 15:43:47 +0530 [thread overview]
Message-ID: <20190414101347.GJ28103@vkoul-mobl> (raw)
In-Reply-To: <20190411192814.10663-1-pierre-louis.bossart@linux.intel.com>
On 11-04-19, 14:28, Pierre-Louis Bossart wrote:
> 0-day/Kbuild starts complaining about missed module dependencies and
> compilation issues. Since codecs and soc drivers need to be compilable
> independently, let's fix this using the following model:
I have not seen a build report on this one, is this some internal Intel
report or on upstream tree?
> SOUNDWIRE_INTEL ---- select -----------
> |
> v
> REGMAP_SOUNDWIRE --- select ---> SOUNDWIRE_BUS
>
>
> Pierre-Louis Bossart (2):
> regmap: soundwire: fix Kconfig select/depend issue
> soundwire: fix SOUNDWIRE_BUS option
>
> drivers/base/regmap/Kconfig | 3 ++-
> drivers/soundwire/Kconfig | 1 -
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> --
> 2.17.1
--
~Vinod
next prev parent reply other threads:[~2019-04-14 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 19:28 [PATCH 0/2] soundwire: fix Kconfig select/depend issues Pierre-Louis Bossart
2019-04-11 19:28 ` [PATCH 1/2] regmap: soundwire: fix Kconfig select/depend issue Pierre-Louis Bossart
2019-04-12 8:38 ` Takashi Iwai
2019-04-12 8:46 ` Mark Brown
2019-04-12 14:07 ` [alsa-devel] " Pierre-Louis Bossart
2019-04-12 14:18 ` Mark Brown
2019-04-12 14:21 ` Takashi Iwai
2019-04-14 10:20 ` Vinod Koul
2019-04-11 19:28 ` [PATCH 2/2] soundwire: fix SOUNDWIRE_BUS option Pierre-Louis Bossart
2019-04-12 10:06 ` [PATCH 0/2] soundwire: fix Kconfig select/depend issues Srinivas Kandagatla
2019-04-12 14:17 ` [alsa-devel] " Pierre-Louis Bossart
2019-04-12 14:27 ` Mark Brown
2019-04-12 14:56 ` Pierre-Louis Bossart
2019-04-14 10:13 ` Vinod Koul [this message]
2019-04-15 12:50 ` 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=20190414101347.GJ28103@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=joe@perches.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
/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