On Wed, Feb 19, 2025 at 01:18:51AM +0000, Kuninori Morimoto wrote: > We should not use (A) today, use (B) instead, but we still have (A) > definition for backword compatibility. > I think we should full switch to use (B), and remove (A). > But it will be too big-patch-set. To avoid patch-bomb, I will post > some of them as sample. I will post full-patch-set if there was no > objection. Yes, we should do the conversion - I've been chipping away at this intermittently myself (mainly for CODECs). If you want to push through the remainder that'd be awesome!
Attachment:
signature.asc
Description: PGP signature
- Follow-Ups:
- Re: [RFC] ASoC: use inclusive language for SND_SOC_DAIFMT_CBx_CFx
- From: Kuninori Morimoto
- Re: [RFC] ASoC: use inclusive language for SND_SOC_DAIFMT_CBx_CFx
- References:
- [RFC] ASoC: use inclusive language for SND_SOC_DAIFMT_CBx_CFx
- From: Kuninori Morimoto
- [RFC] ASoC: use inclusive language for SND_SOC_DAIFMT_CBx_CFx
- Prev by Date: [RFC] ASoC: soc-dai: remove SND_SOC_DAIFMT_CB{MS}_CF{MS}
- Next by Date: Re: [RFC] ASoC: use inclusive language for SND_SOC_DAIFMT_CBx_CFx
- Previous by thread: [RFC] ASoC: soc-dai: remove SND_SOC_DAIFMT_CB{MS}_CF{MS}
- Next by thread: Re: [RFC] ASoC: use inclusive language for SND_SOC_DAIFMT_CBx_CFx
- Index(es):
![]() |