From: David Miller <davem@davemloft.net>
To: bhumirks@gmail.com
Cc: julia.lawall@lip6.fr, sparclinux@vger.kernel.org,
keescook@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc32: mm: srmmu: add __ro_after_init to sparc32_cachetlb_ops structures
Date: Mon, 30 Jan 2017 17:33:13 -0500 (EST) [thread overview]
Message-ID: <20170130.173313.1658478542391677325.davem@davemloft.net> (raw)
In-Reply-To: <1484397114-7705-1-git-send-email-bhumirks@gmail.com>
From: Bhumika Goyal <bhumirks@gmail.com>
Date: Sat, 14 Jan 2017 18:01:54 +0530
> The objects viking_ops, viking_sun4d_smp_ops and smp_cachetlb_ops of
> type sparc32_cachetlb_ops are not modified anywhere after getting modified
> in the init functions. Inside init their reference is also stored in a
> pointer of type const struct sparc32_cachetlb_ops *. So these structures
> are never modified after init, therefore add __ro_after to the declaration
> of these structures.
>
> Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2017-01-30 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 12:31 Bhumika Goyal
2017-01-17 17:33 ` Kees Cook
2017-01-30 22:33 ` David Miller [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=20170130.173313.1658478542391677325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhumirks@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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
all inboxes | Powered by JetHome®