All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
	vkoul@kernel.org, arnd@arndb.de
Subject: Re: [PATCH 0/7] ALSA/ASoC/SOF/SoundWire: fix Kconfig issues
Date: Tue, 02 Mar 2021 15:03:21 +0100	[thread overview]
Message-ID: <s5htuptfyae.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210302003125.1178419-1-pierre-louis.bossart@linux.intel.com>

On Tue, 02 Mar 2021 01:31:18 +0100,
Pierre-Louis Bossart wrote:
> 
> In January, Intel kbuild bot and Arnd Bergmann reported multiple
> issues with randconfig. This patchset builds on Arnd's suggestions to
> 
> a) expose ACPI and PCI devices in separate modules, while sof-acpi-dev
> and sof-pci-dev become helpers. This will result in minor changes
> required for developers/testers, i.e. modprobe snd-sof-pci will no
> longer result in a probe. The SOF CI was already updated to deal with
> this module dependency change and introduction of new modules.
> 
> b) Fix SOF/SoundWire/DSP_config dependencies by moving the code
> required to detect SoundWire presence in ACPI tables to sound/hda.
> 
> Integration note:
> This patchset touches directories maintained by Vinod, Takashi and
> Mark in separate trees, and will impact additional changes to use the
> auxiliary bus in drivers/soundwire/.
> I can think of two options, both of which are fine:
> 1. Mark merges the patches with Vinod and Takashi Acked-by tags, then
> Mark provides an immutable tag to Vinod.
> 2. Vinod merges the patches with Mark and Takashi Acked-by tags, then
> Vinod provides an immutable tag to Mark

Acked-by: Takashi Iwai <tiwai@suse.de>


thanks,

Takashi

  parent reply	other threads:[~2021-03-02 14:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  0:31 [PATCH 0/7] ALSA/ASoC/SOF/SoundWire: fix Kconfig issues Pierre-Louis Bossart
2021-03-02  0:31 ` [PATCH 1/7] ASoC: soc-acpi: allow for partial match in parent name Pierre-Louis Bossart
2021-03-02  0:31 ` [PATCH 2/7] ASoC: SOF: ACPI: avoid reverse module dependency Pierre-Louis Bossart
2021-03-02  0:31 ` [PATCH 3/7] ASoC: SOF: pci: split PCI into different drivers Pierre-Louis Bossart
2021-03-02  0:31 ` [PATCH 4/7] ASoC: SOF: pci: move DSP_CONFIG use to platform-specific drivers Pierre-Louis Bossart
2021-03-02  0:31 ` [PATCH 5/7] ASoC: SOF: Intel: SoundWire: simplify Kconfig Pierre-Louis Bossart
2021-03-02  0:31 ` [PATCH 6/7] ALSA: hda: move Intel SoundWire ACPI scan to dedicated module Pierre-Louis Bossart
2021-03-02 14:12   ` Vinod Koul
2021-03-02  0:31 ` [PATCH 7/7] ALSA: hda: intel-sdw-acpi: add missing include files Pierre-Louis Bossart
2021-03-02 12:43 ` [PATCH 0/7] ALSA/ASoC/SOF/SoundWire: fix Kconfig issues Mark Brown
2021-03-02 14:03 ` Takashi Iwai [this message]
2021-03-02 14:13   ` Vinod Koul
2021-03-02 14:43     ` Takashi Iwai
2021-03-02 14:52       ` Pierre-Louis Bossart
2021-03-02 15:03       ` Mark Brown
2021-03-02 15:16         ` Takashi Iwai
2021-03-02 15:34           ` Mark Brown
2021-07-26 18:59 ` Arnd Bergmann
2021-07-26 21:01   ` Pierre-Louis Bossart
2021-07-26 21:33     ` Arnd Bergmann
2021-07-28 15:39       ` Arnd Bergmann

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=s5htuptfyae.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=vkoul@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.