From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: gpio: fix const issue in spi_to_spi_gpio()
Date: Thu, 22 May 2025 14:38:01 +0100 [thread overview]
Message-ID: <174792108102.84499.9131453777647011628.b4-ty@kernel.org> (raw)
In-Reply-To: <2025052225-scallion-ritzy-dbbd@gregkh>
On Thu, 22 May 2025 12:57:26 +0200, Greg Kroah-Hartman wrote:
> While the struct spi_device * passed into spi_to_spi_gpio() is a const
> one, the struct spi_bitbang * that is retrieved from the controller
> field in the spi_device is NOT a const pointer, as it is coming from the
> spi_controller_get_devdata() call, and then passed to container_of()
> which would strip off the const attribute for no good reason (i.e. if a
> const pointer is passed to container_of() it still is const coming out).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: gpio: fix const issue in spi_to_spi_gpio()
commit: 2712a7d362904d0c4283ae91fac8cea6ecd6f9c2
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
prev parent reply other threads:[~2025-05-22 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 10:57 [PATCH] spi: gpio: fix const issue in spi_to_spi_gpio() Greg Kroah-Hartman
2025-05-22 13:38 ` 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=174792108102.84499.9131453777647011628.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox