All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>,
	broonie@kernel.org, peter.ujfalusi@linux.intel.com,
	yung-chuan.liao@linux.intel.com
Cc: kai.vehmanen@linux.intel.com, cezary.rojewski@intel.com,
	ranjani.sridharan@linux.intel.com, alsa-devel@alsa-project.org,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH v3] ASoC: Intel: soc-acpi-intel-tgl-match: add cs42l43 and cs35l56 support
Date: Mon, 4 Dec 2023 10:44:08 -0600	[thread overview]
Message-ID: <041f60ab-a90a-4654-afd2-c2a296a25c46@linux.intel.com> (raw)
In-Reply-To: <f2dec209-6bc7-49ab-9dff-57a2ca4efb03@opensource.cirrus.com>


>> Don't we need the same change of name_prefix for
>> soc-acpi-intel-mtl-match.c? I see this in the existing code:
>>
> 
> The chain that Peter sent only has CS35L56 added to tgl-match.
> 
> I've checked the history of mtl-match and the patch that added CS35L56
> there was not cc'd to any cirrus.com email address so we didn't notice
> it. Otherwise we would have picked this up earlier. alsa-devel is noisy.
> 
> I haven't got a MTL platform to test on but I can send a separate patch
> to change mtl-match if you are happy with this prefix change.

That would be nice, best to align on all platforms and use the same the
same prefix.

  reply	other threads:[~2023-12-04 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 13:56 [PATCH v3] ASoC: Intel: soc-acpi-intel-tgl-match: add cs42l43 and cs35l56 support Richard Fitzgerald
2023-12-04 14:55 ` Pierre-Louis Bossart
2023-12-04 15:54   ` Richard Fitzgerald
2023-12-04 16:44     ` Pierre-Louis Bossart [this message]
2023-12-05 13:11 ` 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=041f60ab-a90a-4654-afd2-c2a296a25c46@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=rf@opensource.cirrus.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.