All of lore.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: cujomalainey@chromium.org, alsa-devel@alsa-project.org
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Trevor Wu <trevor.wu@mediatek.com>,
	Tinghan Shen <tinghan.shen@mediatek.com>
Subject: Re: [PATCH] ASoC: SOF: mediatek: mt8186: Revert Add Google Steelix topology compatible
Date: Wed, 6 Dec 2023 15:32:29 +0100	[thread overview]
Message-ID: <b441c416-91aa-4723-a605-a58974dcc444@collabora.com> (raw)
In-Reply-To: <20231205220131.2585913-1-cujomalainey@chromium.org>

Il 05/12/23 23:01, cujomalainey@chromium.org ha scritto:
> From: Curtis Malainey <cujomalainey@chromium.org>
> 
> This reverts commit 505c83212da5bfca95109421b8f5d9f8c6cdfef2.
> 
> This is not an official topology from the SOF project. Topologies are
> named based on the card configuration and are NOT board specific.
> 

While I can totally agree with that, can you please explain how should the correct
topology file name be selected instead of machine compatibles?

Thanks,
Angelo


  parent reply	other threads:[~2023-12-06 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 22:01 [PATCH] ASoC: SOF: mediatek: mt8186: Revert Add Google Steelix topology compatible cujomalainey
2023-12-06 14:21 ` Mark Brown
2023-12-06 18:51   ` Curtis Malainey
2023-12-06 14:32 ` AngeloGioacchino Del Regno [this message]
2023-12-06 18:21   ` Curtis Malainey
2023-12-06 21:04 ` Mark Brown

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=b441c416-91aa-4723-a605-a58974dcc444@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cujomalainey@chromium.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tinghan.shen@mediatek.com \
    --cc=tiwai@suse.com \
    --cc=trevor.wu@mediatek.com \
    --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 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.