All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, Yang Yingliang <yangyingliang@huawei.com>
Cc: geert@linux-m68k.org, lukas@wunner.de
Subject: Re: (subset) [PATCH -next v2 00/21] spi: switch to use modern name (part1)
Date: Mon, 07 Aug 2023 22:57:30 +0100	[thread overview]
Message-ID: <169144545021.329334.17124295830749612007.b4-ty@kernel.org> (raw)
In-Reply-To: <20230807140717.3484180-1-yangyingliang@huawei.com>

On Mon, 07 Aug 2023 22:06:56 +0800, Yang Yingliang wrote:
> I'm trying to rename the legacy name to modern name used in SPI drivers,
> this is part1 patchset.
> 
> After introducing devm_spi_alloc_host/spi_alloc_host(), the legacy
> named function devm_spi_alloc_master/spi_alloc_master() can be replaced.
> And also change other legacy name master/slave to modern name host/target
> or controller. Each patch compile test passed.
> 
> [...]

Applied to

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

Thanks!

[10/21] spi: cadence-quadspi: switch to use modern name
        commit: 1c75d749b5ebd2352cc72ed33d4fb522c624d974

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


      parent reply	other threads:[~2023-08-07 21:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 14:06 [PATCH -next v2 00/21] spi: switch to use modern name (part1) Yang Yingliang
2023-08-07 14:06 ` [PATCH -next v2 01/21] spi: amd: switch to use modern name Yang Yingliang
2023-08-07 14:06 ` [PATCH -next v2 02/21] spi: aspeed: " Yang Yingliang
2023-08-07 14:06 ` [PATCH -next v2 03/21] spi: spi-axi-spi-engine: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 04/21] spi: bcm-qspi: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 05/21] spi: bcm2835: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 06/21] spi: bcm2835aux: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 07/21] spi: bcm63xx-hsspi: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 08/21] spi: bcm63xx: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 09/21] spi: butterfly: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 10/21] spi: cadence-quadspi: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 11/21] spi: cadence-xspi: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 12/21] spi: cadence: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 13/21] spi: clps711x: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 14/21] spi: octeon: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 15/21] spi: spi-cavium-thunderx: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 16/21] spi: coldfire-qspi: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 17/21] spi: davinci: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 18/21] spi: dln2: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 19/21] spi: dw: " Yang Yingliang
2023-08-15 11:36   ` Geert Uytterhoeven
2023-08-16  3:45     ` Yang Yingliang
2023-08-16  7:17       ` Geert Uytterhoeven
2023-08-16  9:38         ` Serge Semin
2023-08-16 10:03           ` Geert Uytterhoeven
2023-08-16  9:24       ` Serge Semin
2023-08-16  9:29         ` Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 20/21] spi: hisi-kunpeng: " Yang Yingliang
2023-08-07 14:07 ` [PATCH -next v2 21/21] spi: npcm-fiu: " Yang Yingliang
2023-08-07 21:57 ` Mark Brown [this message]

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=169144545021.329334.17124295830749612007.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=yangyingliang@huawei.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.