From: Kees Cook <keescook@chromium.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Make debug_obj_descr const
Date: Wed, 19 Aug 2020 12:52:26 -0700 [thread overview]
Message-ID: <202008191251.B7EDB6FA3@keescook> (raw)
In-Reply-To: <20200815004027.2046113-1-swboyd@chromium.org>
On Fri, Aug 14, 2020 at 05:40:25PM -0700, Stephen Boyd wrote:
> These patches make debug_obj_descr into a const pointer. The second
> patch can be split up into many patches if desired and sent to
> respective susbsytem maintainers.
>
> Stephen Boyd (2):
> debugobjects: Allow debug_obj_descr to be const
> treewide: Make all debug_obj_descr's const
>
> drivers/gpu/drm/i915/i915_active.c | 2 +-
> drivers/gpu/drm/i915/i915_sw_fence.c | 2 +-
> include/linux/debugobjects.h | 32 ++++++++++++++--------------
> kernel/rcu/rcu.h | 2 +-
> kernel/rcu/update.c | 2 +-
> kernel/time/hrtimer.c | 4 ++--
> kernel/time/timer.c | 4 ++--
> kernel/workqueue.c | 4 ++--
> lib/debugobjects.c | 30 +++++++++++++-------------
> lib/percpu_counter.c | 4 ++--
> 10 files changed, 43 insertions(+), 43 deletions(-)
Yay more read-only memory! :)
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
prev parent reply other threads:[~2020-08-19 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 0:40 [PATCH 0/2] Make debug_obj_descr const Stephen Boyd
2020-08-15 0:40 ` [PATCH 1/2] debugobjects: Allow debug_obj_descr to be const Stephen Boyd
2020-09-24 19:58 ` [tip: core/debugobjects] " tip-bot2 for Stephen Boyd
2020-08-15 0:40 ` [PATCH 2/2] treewide: Make all debug_obj_descr's const Stephen Boyd
2020-09-24 19:58 ` [tip: core/debugobjects] treewide: Make all debug_obj_descriptors const tip-bot2 for Stephen Boyd
2020-08-19 19:52 ` Kees Cook [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=202008191251.B7EDB6FA3@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
/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