From: Geoff Levand <geoff@infradead.org>
To: "Ricardo B. Marliere" <ricardo@marliere.net>,
Arnd Bergmann <arnd@arndb.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] powerpc: ps3: make ps3_system_bus_type const
Date: Mon, 5 Feb 2024 09:04:00 +0900 [thread overview]
Message-ID: <04c1b434-2ae6-401d-93ff-61641e1396af@infradead.org> (raw)
In-Reply-To: <20240204-bus_cleanup-powerpc-v1-2-c763f0e142e9@marliere.net>
On 2/4/24 23:21, Ricardo B. Marliere wrote:
> Now that the driver core can properly handle constant struct bus_type,
> move the ps3_system_bus_type variable to be a constant structure as
> well, placing it into read-only memory which can not be modified at
> runtime.
> -static struct bus_type ps3_system_bus_type = {
> +static const struct bus_type ps3_system_bus_type = {
> .name = "ps3_system_bus",
> .match = ps3_system_bus_match,
> .uevent = ps3_system_bus_uevent,
Seems fine.
Acked-by: Geoff Levand <geoff@infradead.org>
next prev parent reply other threads:[~2024-02-05 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 14:21 [PATCH 0/4] powerpc: struct bus_type cleanup Ricardo B. Marliere
2024-02-04 14:21 ` [PATCH 1/4] powerpc: cell: make spu_subsys const Ricardo B. Marliere
2024-02-04 14:21 ` [PATCH 2/4] powerpc: ps3: make ps3_system_bus_type const Ricardo B. Marliere
2024-02-04 20:47 ` Geert Uytterhoeven
2024-02-05 0:04 ` Geoff Levand [this message]
2024-02-04 14:21 ` [PATCH 3/4] powerpc: pseries: make cmm_subsys const Ricardo B. Marliere
2024-02-04 14:21 ` [PATCH 4/4] powerpc: pseries: make suspend_subsys const Ricardo B. Marliere
2024-02-04 14:38 ` [PATCH 0/4] powerpc: struct bus_type cleanup Greg Kroah-Hartman
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=04c1b434-2ae6-401d-93ff-61641e1396af@infradead.org \
--to=geoff@infradead.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ricardo@marliere.net \
/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;
as well as URLs for NNTP newsgroup(s).