[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170016612386.72552.14423257472508429993.b4-ty@kernel.org>
Date: Thu, 16 Nov 2023 20:22:03 +0000
From: Mark Brown <broonie@...nel.org>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Yang Yingliang <yangyingliang@...wei.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org, netdev@...r.kernel.org,
linux-usb@...r.kernel.org, linux-spi@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH v1 1/1] treewide, spi: Get rid of
SPI_MASTER_HALF_DUPLEX
On Mon, 13 Nov 2023 13:12:49 +0200, Andy Shevchenko wrote:
> The SPI_MASTER_HALF_DUPLEX is the legacy name of a definition
> for a half duplex flag. Since all others had been replaced with
> the respective SPI_CONTROLLER prefix get rid of the last one
> as well. There is no functional change intended.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] treewide, spi: Get rid of SPI_MASTER_HALF_DUPLEX
commit: 3fc6350fc8470d42f5e700ecd1c3d90f9dd9fd2d
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
Powered by blists - more mailing lists