public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Mark Brown <broonie@kernel.org>
Cc: shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
	nicoleotsuka@gmail.com, james.schulman@cirrus.com,
	david.rhodes@cirrus.com, rf@opensource.cirrus.com,
	linuxppc-dev@lists.ozlabs.org, perex@perex.cz, tiwai@suse.com,
	alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
	patches@opensource.cirrus.com, paul.gortmaker@windriver.com
Subject: Re: [PATCH 2/2] ASoC: cs4270: Remove unused codec
Date: Thu, 23 Nov 2023 11:22:07 +1100	[thread overview]
Message-ID: <877cm9s4i8.fsf@mail.lhotse> (raw)
In-Reply-To: <ZV3pIb1p52CFNsSl@finisterre.sirena.org.uk>

Mark Brown <broonie@kernel.org> writes:
> On Wed, Nov 22, 2023 at 05:27:12PM +1100, Michael Ellerman wrote:
>> The only driver to enable SND_SOC_CS4270 was SND_SOC_MPC8610_HPCD, which
>> was dropped in the preceding commit. Remove the codec as unused.
>
> There's no real overhead from having extra drivers and we do have
> generic drivers that people can attach CODECs to.

OK. I have no idea how sound works, I was just cleaning things up. So
whatever you think is best.

cheers

  reply	other threads:[~2023-11-23  0:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  6:27 [PATCH 1/2] ASoC: fsl: mpc8610_hpcd: Remove unused driver Michael Ellerman
2023-11-22  6:27 ` [PATCH 2/2] ASoC: cs4270: Remove unused codec Michael Ellerman
2023-11-22 11:42   ` Mark Brown
2023-11-23  0:22     ` Michael Ellerman [this message]
2023-11-23 10:36 ` (subset) [PATCH 1/2] ASoC: fsl: mpc8610_hpcd: Remove unused driver 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=877cm9s4i8.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=david.rhodes@cirrus.com \
    --cc=festevam@gmail.com \
    --cc=james.schulman@cirrus.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=patches@opensource.cirrus.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=shengjiu.wang@gmail.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