From: Arnd Bergmann <arnd@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-kernel @ vger . kernel . org"
<linux-kernel@vger.kernel.org>, Takashi Iwai <tiwai@suse.com>,
YueHaibing <yuehaibing@huawei.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Mark Brown <broonie@kernel.org>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
sound-open-firmware@alsa-project.org
Subject: Re: [Sound-open-firmware] [PATCH] ASoC: SOF: Intel: avoid reverse module dependency
Date: Tue, 12 Jan 2021 21:31:40 +0100 [thread overview]
Message-ID: <CAK8P3a3eOt_5cYsJQuTtFJqLpX0ZS_GGk=x-pJk4Lg=mdVX-_g@mail.gmail.com> (raw)
In-Reply-To: <ed4b4b5b-0cde-3d08-bbbf-3f0d90ce46ea@linux.intel.com>
On Tue, Jan 12, 2021 at 9:17 PM Pierre-Louis Bossart
<pierre-louis.bossart@linux.intel.com> wrote:
>
>
> >> Since this is going to be a really invasive change, and past
> >> experience shows that mucking with Kconfigs will invariably raise a
> >> number of broken corner cases, if there is support from
> >> Mark/Takashi/Jaroslav on this idea, we should first test it in the SOF
> >> tree so that we get a good test coverage and don't break too many eggs
> >> in Mark's tree. We would also need to concurrently change our CI
> >> scripts which are dependent on module names.
> >
> > I'm in favor of the way Arnd proposed. It's more straightforward and
> > less code.
>
> Thanks Takashi for the feedback.
>
> Since yesterday I looked at another problem where we can have unmet
> dependencies between SoundWire (m) and SOF (y), so we probably need to
> rethink all this. We had similar issue with SOF and HDaudio before, it's
> time to revisit all this.
I think I ran into the same thing yesterday, and came up with a patch for
that one as well. I think it should be independent of the other one but I did
not try it by itself.
I'll send it along with a fixed version of the one in this thread, together the
have now survived a few hundred randconfig builds.
Arnd
next prev parent reply other threads:[~2021-01-12 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 13:52 [PATCH] ALSA: hda: fix SND_INTEL_DSP_CONFIG dependency Arnd Bergmann
2021-01-04 14:09 ` Takashi Iwai
2021-01-04 14:13 ` Mark Brown
2021-01-04 15:00 ` Jaroslav Kysela
2021-01-04 15:05 ` Takashi Iwai
2021-01-05 13:43 ` Arnd Bergmann
2021-01-05 15:39 ` Kai Vehmanen
2021-01-05 19:06 ` Arnd Bergmann
2021-01-05 19:07 ` [PATCH] ASoC: SOF: Intel: avoid reverse module dependency Arnd Bergmann
2021-01-06 9:30 ` Arnd Bergmann
2021-01-07 11:45 ` Kai Vehmanen
2021-01-11 19:54 ` Pierre-Louis Bossart
2021-01-12 13:55 ` Takashi Iwai
2021-01-12 20:17 ` [Sound-open-firmware] " Pierre-Louis Bossart
2021-01-12 20:31 ` Arnd Bergmann [this message]
2021-01-05 13:30 ` [PATCH] ALSA: hda: fix SND_INTEL_DSP_CONFIG dependency 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='CAK8P3a3eOt_5cYsJQuTtFJqLpX0ZS_GGk=x-pJk4Lg=mdVX-_g@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).