From: Tony Lindgren <tony@atomide.com>
To: "Ricardo B. Marliere" <ricardo@marliere.net>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] bus: ti-sysc: constify the struct device_type usage
Date: Wed, 28 Feb 2024 09:31:02 +0200 [thread overview]
Message-ID: <20240228073102.GE52537@atomide.com> (raw)
In-Reply-To: <20240219-device_cleanup-ti-sysc-v1-1-13b53177d0a5@marliere.net>
* Ricardo B. Marliere <ricardo@marliere.net> [240219 14:09]:
> Since commit aed65af1cc2f ("drivers: make device_type const"), the driver
> core can properly handle constant struct device_type. Move the
> sysc_device_type variable to be a constant structure as well, placing it
> into read-only memory which can not be modified at runtime.
Thanks applying into omap-for-v6.9/ti-sysc.
Tony
prev parent reply other threads:[~2024-02-28 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 12:10 [PATCH] bus: ti-sysc: constify the struct device_type usage Ricardo B. Marliere
2024-02-28 7:31 ` Tony Lindgren [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=20240228073102.GE52537@atomide.com \
--to=tony@atomide.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).