linux-kernel - Re: [PATCH] Documentation: spi: Update the "master/slave" terminology

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <170801614576.198390.7530746643717040868.b4-ty@kernel.org>
Date: Thu, 15 Feb 2024 16:55:45 +0000
From: Mark Brown <broonie@...nel.org>
To: Dhruva Gole <d-gole@...com>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>, theo.lebrun@...tlin.com, 
 linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: spi: Update the "master/slave"
 terminology

On Thu, 15 Feb 2024 14:24:05 +0530, Dhruva Gole wrote:
> Update the master/slave terminology wherever possible to adopt usage of
> the controller/host/target. Some parts have been left untouched because
> they were sysfs entries and will probably end up being inaccurate if
> simply replaced here.
> 
> 

Applied to

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

Thanks!

[1/1] Documentation: spi: Update the "master/slave" terminology
      commit: 99769a52464d9f4c3b44bf903d08743cd53c49f6

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