From: Stephen Boyd <sboyd@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] clk: ep93xx: make const read-only arrays static
Date: Mon, 13 Jan 2025 13:28:37 -0800 [thread overview]
Message-ID: <b2cdc665f44521dca41d328b87b2febb.sboyd@kernel.org> (raw)
In-Reply-To: <20250112213947.8524-1-colin.i.king@gmail.com>
Quoting Colin Ian King (2025-01-12 13:39:47)
> Don't populate the const read-only arrays on the stack at run time,
> instead make them static.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2025-01-13 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 21:39 [PATCH][next] clk: ep93xx: make const read-only arrays static Colin Ian King
2025-01-13 21:28 ` Stephen Boyd [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=b2cdc665f44521dca41d328b87b2febb.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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;
as well as URLs for NNTP newsgroup(s).