From: Matthew Wilcox <willy@infradead.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Joel Granados" <joel.granados@kernel.org>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Kees Cook" <kees@kernel.org>,
"Luis Chamberlain" <mcgrof@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
linux-crypto@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, linux-hyperv@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-raid@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-serial@vger.kernel.org,
xen-devel@lists.xenproject.org, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, netfs@lists.linux.dev,
codalist@coda.cs.cmu.edu, linux-mm@kvack.org,
linux-nfs@vger.kernel.org, ocfs2-devel@lists.linux.dev,
fsverity@lists.linux.dev, linux-xfs@vger.kernel.org,
io-uring@vger.kernel.org, bpf@vger.kernel.org,
kexec@lists.infradead.org, linux-trace-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, apparmor@lists.ubuntu.com,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
"Song Liu" <song@kernel.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
"Corey Minyard" <cminyard@mvista.com>
Subject: Re: Re: Re: [PATCH v2] treewide: const qualify ctl_tables where applicable
Date: Mon, 27 Jan 2025 15:42:39 +0000 [thread overview]
Message-ID: <Z5epb86xkHQ3BLhp@casper.infradead.org> (raw)
In-Reply-To: <87jzag9ugx.fsf@intel.com>
On Mon, Jan 27, 2025 at 04:55:58PM +0200, Jani Nikula wrote:
> You could have static const within functions too. You get the rodata
> protection and function local scope, best of both worlds?
timer_active is on the stack, so it can't be static const.
Does this really need to be cc'd to such a wide distribution list?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-01-27 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 14:16 [PATCH v2] treewide: const qualify ctl_tables where applicable Joel Granados
2025-01-10 18:28 ` Anna Schumaker
2025-01-12 10:36 ` Baoquan He
2025-01-15 17:52 ` Thomas Gleixner
2025-01-15 20:09 ` Wei Liu
2025-01-15 20:30 ` Bill O'Donnell
2025-01-21 13:40 ` Alexander Gordeev
2025-01-22 12:25 ` Joel Granados
2025-01-22 12:41 ` Ard Biesheuvel
2025-01-27 13:49 ` Joel Granados
2025-01-27 14:55 ` Jani Nikula
2025-01-27 15:42 ` Matthew Wilcox [this message]
2025-01-28 11:22 ` Joel Granados
2025-01-28 15:43 ` Paul Moore
2025-01-29 8:49 ` Joel Granados
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=Z5epb86xkHQ3BLhp@casper.infradead.org \
--to=willy@infradead.org \
--cc=agordeev@linux.ibm.com \
--cc=apparmor@lists.ubuntu.com \
--cc=ardb@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cminyard@mvista.com \
--cc=codalist@coda.cs.cmu.edu \
--cc=djwong@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fsverity@lists.linux.dev \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=io-uring@vger.kernel.org \
--cc=jani.nikula@intel.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-aio@kvack.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=mcgrof@kernel.org \
--cc=netfs@lists.linux.dev \
--cc=ocfs2-devel@lists.linux.dev \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).