From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <groeck@google.com>
Cc: pierre-louis.bossart@linux.intel.com,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>,
"Patel, Chintan M" <chintan.m.patel@intel.com>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files
Date: Wed, 23 May 2018 10:49:28 +0100 [thread overview]
Message-ID: <20180523094928.GE4828@sirena.org.uk> (raw)
In-Reply-To: <CABXOdTd5+QJHOZ6BcSO-TfJCqcLzdd+Gbnf4HYh9i9cG+UH+1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Tue, May 22, 2018 at 02:59:50PM -0700, Guenter Roeck wrote:
> Most people are not aware that they have a backwards compatibility problem
> with the topology file. They will typically notice and report that it is
> impossible to get audio working with an upstream kernel on a recent
> Chromebook, and as users they rarely know about development mailing lists.
> Some technical discussions are at
> https://github.com/GalliumOS/galliumos-distro/issues/379
> https://github.com/GalliumOS/galliumos-distro/issues/274
> though I had seen others earlier. Guess next time I'll have to preserve
> links. Anyway, I am not really much interested in an argument/discussion
> about my use of the term "widely". I'll rephrase that paragraph in the next
> version of the patch, should it come to that.
Right, looks like the disconnect I thought it was - this has been
discussed a lot within your distro (and possibly others) but not outside
it so the rest of us are all a bit surprised.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-23 9:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 16:58 [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files Guenter Roeck
2018-05-22 17:14 ` Mark Brown
2018-05-22 19:59 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 8:24 ` Mark Brown
2018-05-23 13:42 ` Pierre-Louis Bossart
2018-05-23 13:56 ` Takashi Iwai
[not found] ` <CABXOdTdGyfBdZUzG-DzGgfr0Afrh9dtgdXibQreOZm7nb4z3=w@mail.gmail.com>
2018-05-23 14:58 ` Takashi Iwai
2018-05-23 15:52 ` Mark Brown
[not found] ` <CABXOdTd5+QJHOZ6BcSO-TfJCqcLzdd+Gbnf4HYh9i9cG+UH+1g@mail.gmail.com>
2018-05-23 9:49 ` Mark Brown [this message]
2018-05-23 13:54 ` Takashi Iwai
2018-05-23 13:56 ` Mark Brown
[not found] ` <CABXOdTeCr-ExO9O3XAHK-DnNf5yLGO0TPkXgs60TB90jGNB2_Q@mail.gmail.com>
2018-05-23 15:58 ` Mark Brown
2018-05-23 16:17 ` Guenter Roeck
2018-05-24 9:52 ` Takashi Iwai
2018-05-24 14:18 ` Mark Brown
2018-05-24 14:55 ` Guenter Roeck
2018-05-24 15:11 ` Mark Brown
2018-05-25 9:04 ` [alsa-devel] " Lin, Mengdong
2018-05-25 13:20 ` Guenter Roeck
2018-05-23 16:29 ` Guenter Roeck
2018-05-23 20:28 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 21:22 ` Guenter Roeck
2018-05-24 3:38 ` Pierre-Louis Bossart
2018-05-25 13:40 ` Shreyas NC
2018-05-25 14:09 ` Guenter Roeck
2018-05-25 17:41 ` Guenter Roeck
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=20180523094928.GE4828@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=chintan.m.patel@intel.com \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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