From: Will Deacon <will@kernel.org>
To: Rikard Falkeborn <rikard.falkeborn@gmail.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Shaokun Zhang <zhangshaokun@hisilicon.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Frank Li <Frank.li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Andy Gross <agross@kernel.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH 0/4] drivers/perf: Constify static struct attribute_group
Date: Wed, 20 Jan 2021 18:13:01 +0000 [thread overview]
Message-ID: <161116508323.2646977.9881871665706289493.b4-ty@kernel.org> (raw)
In-Reply-To: <20210117212847.21319-1-rikard.falkeborn@gmail.com>
On Sun, 17 Jan 2021 22:28:43 +0100, Rikard Falkeborn wrote:
> Thie series makes a number of static struct attribute_group const. The
> only usage of the structs is to put their address in an array of pointers
> to const struct * attribute_group. With this series applied, all but two
> static struct attribute_group in drivers/perf are const (and the two
> remaining are modified at runtime and can't be const).
>
> Patches are independent and split based on output from get_maintainers.pl.
> I can of course split differently if that's desired.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/4] perf: qcom: Constify static struct attribute_group
https://git.kernel.org/will/c/30b34c4833ea
[2/4] perf/imx_ddr: Constify static struct attribute_group
https://git.kernel.org/will/c/3cb7d2da183f
[3/4] perf: hisi: Constify static struct attribute_group
https://git.kernel.org/will/c/c2c4d5c051b2
[4/4] perf: Constify static struct attribute_group
https://git.kernel.org/will/c/f0c140481d1b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-01-20 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 21:28 Rikard Falkeborn
2021-01-17 21:28 ` [PATCH 1/4] perf: qcom: " Rikard Falkeborn
2021-01-17 21:28 ` [PATCH 2/4] perf/imx_ddr: " Rikard Falkeborn
2021-01-17 21:28 ` [PATCH 3/4] perf: hisi: " Rikard Falkeborn
2021-01-17 21:28 ` [PATCH 4/4] perf: " Rikard Falkeborn
2021-01-20 18:13 ` Will Deacon [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=161116508323.2646977.9881871665706289493.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Frank.li@nxp.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=festevam@gmail.com \
--cc=kernel-team@android.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rikard.falkeborn@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=zhangshaokun@hisilicon.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
all inboxes | Powered by JetHome®