From: Mark Brown <broonie@kernel.org>
To: Min Li <min.li.xe@renesas.com>, Lee Jones <lee@kernel.org>,
Vladimir Oltean <olteanv@gmail.com>,
Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>,
Michal Simek <michal.simek@amd.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/6] spi: struct spi_device constification
Date: Mon, 13 Mar 2023 18:20:21 +0000 [thread overview]
Message-ID: <167873162127.102913.8422691549398667827.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1678704562.git.geert+renesas@glider.be>
On Mon, 13 Mar 2023 11:58:32 +0100, Geert Uytterhoeven wrote:
> Hi all,
>
> After noticing new cases of casting away constness, I went over all
> spi_get_*() functions and their callers, and made the following changes:
> 1. Make all pointer parameters const where possible,
> 2. Remove unneeded casts, some not even related to constness.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[2/6] spi: fsl-dspi: Remove unneeded cast to same type
commit: 9c8400e3795decefe6390646ece820a310b37b79
[3/6] spi: Constify spi_get_ctldata()'s spi parameter
commit: cc4b15670340315fb0b25d886c06bffb5f128f02
[4/6] spi: Constify spi_get_drvdata()'s spi parameter
commit: 38dca04d659a422d842f7edcecd32253c7a6fb5e
[5/6] spi: Constify spi parameters of chip select APIs
commit: d2f19eec510424caa55ea949f016ddabe2d8173a
[6/6] spi: sh-msiof: Remove casts to drop constness
commit: 7859ad5a401b73bf2ddfa274950b5722492c3150
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:[~2023-03-13 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 10:58 [PATCH 0/6] spi: struct spi_device constification Geert Uytterhoeven
2023-03-13 10:58 ` [PATCH 1/6] mfd: rsmu_spi: Remove unneeded casts of void * Geert Uytterhoeven
2023-03-16 16:13 ` Lee Jones
2023-03-13 10:58 ` [PATCH 2/6] spi: fsl-dspi: Remove unneeded cast to same type Geert Uytterhoeven
2023-03-13 10:58 ` [PATCH 3/6] spi: Constify spi_get_ctldata()'s spi parameter Geert Uytterhoeven
2023-03-13 10:58 ` [PATCH 4/6] spi: Constify spi_get_drvdata()'s " Geert Uytterhoeven
2023-03-13 10:58 ` [PATCH 5/6] spi: Constify spi parameters of chip select APIs Geert Uytterhoeven
2023-03-13 10:58 ` [PATCH 6/6] spi: sh-msiof: Remove casts to drop constness Geert Uytterhoeven
2023-03-13 18:20 ` 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=167873162127.102913.8422691549398667827.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=amit.kumar-mahapatra@amd.com \
--cc=geert+renesas@glider.be \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=min.li.xe@renesas.com \
--cc=olteanv@gmail.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.