mbox series

[0/3] ASoC: sh: remove discriminatory terms

Message ID 87r1tg3swv.wl-kuninori.morimoto.gx@renesas.com (mailing list archive)
Headers show
Series ASoC: sh: remove discriminatory terms | expand

Message

Kuninori Morimoto July 13, 2020, 5:07 a.m. UTC
rsnd / fsi are using discriminatory terms.
This patch-set removes it as much as possible.
But, because DMA related API function name, it still exists.
I hope all these are removed someday.

Kuninori Morimoto (3):
  ASoC: rsnd: don't use discriminatory terms for function names
  ASoC: rsnd: don't use discriminatory terms for comment
  ASoC: fsi: don't use discriminatory terms for comment

 sound/soc/sh/fsi.c       |  4 ++--
 sound/soc/sh/rcar/core.c |  4 ++--
 sound/soc/sh/rcar/rsnd.h |  2 +-
 sound/soc/sh/rcar/ssi.c  | 28 ++++++++++++++--------------
 sound/soc/sh/rcar/ssiu.c |  6 +++---
 5 files changed, 22 insertions(+), 22 deletions(-)

Comments

Mark Brown July 14, 2020, 4:39 p.m. UTC | #1
On 13 Jul 2020 14:07:43 +0900, Kuninori Morimoto wrote:
> rsnd / fsi are using discriminatory terms.
> This patch-set removes it as much as possible.
> But, because DMA related API function name, it still exists.
> I hope all these are removed someday.
> 
> Kuninori Morimoto (3):
>   ASoC: rsnd: don't use discriminatory terms for function names
>   ASoC: rsnd: don't use discriminatory terms for comment
>   ASoC: fsi: don't use discriminatory terms for comment
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/3] ASoC: rsnd: don't use discriminatory terms for function names
      commit: 25b384b8eabb65bc6546dc2e98e93816dd734a52
[2/3] ASoC: rsnd: don't use discriminatory terms for comment
      commit: f7c7a24b7d0c94f7f0fdaac08c25772e152bfed1
[3/3] ASoC: fsi: don't use discriminatory terms for comment
      commit: cf01245db89922e4ec2404aaf527ca3d567c4e5e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark