From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Rosen Penev <rosenp@gmail.com>, linux-wireless@vger.kernel.org
Cc: open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 ath-next] wifi: ath9k: mark static arrays as const
Date: Mon, 22 Jun 2026 13:49:28 +0200 [thread overview]
Message-ID: <87se6eeqwn.fsf@toke.dk> (raw)
In-Reply-To: <20260619175210.5348-1-rosenp@gmail.com>
Rosen Penev <rosenp@gmail.com> writes:
> PN9Data is a read-only lookup table and is never modified. Adding const
> lets the compiler place it in .rodata and prevents accidental writes.
>
> Use the same treatment for bits_per_symbol. It's not modified either.
>
> Assisted-by: opencode:big-pickle
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Again, which actual bug are you fixing here?
-Toke
prev parent reply other threads:[~2026-06-22 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 17:52 [PATCHv2 ath-next] wifi: ath9k: mark static arrays as const Rosen Penev
2026-06-22 11:49 ` Toke Høiland-Jørgensen [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=87se6eeqwn.fsf@toke.dk \
--to=toke@toke.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rosenp@gmail.com \
/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