From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Fabian Frederick <fabf@skynet.be>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
박경민 <kyungmin.park@samsung.com>, "Kukjin Kim" <kgene@kernel.org>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Alexandre Courbot" <gnurou@gmail.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 30/35 linux-next] devfreq: constify of_device_id array
Date: Tue, 17 Mar 2015 01:11:51 +0000 (GMT) [thread overview]
Message-ID: <487895027.183321426554710978.JavaMail.weblogic@epmlwas07d> (raw)
> of_device_id is always used as const.
> (See driver.of_match_table and open firmware functions)
>
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
> ---
> drivers/devfreq/event/exynos-ppmu.c | 2 +-
> drivers/devfreq/tegra-devfreq.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/devfreq/event/exynos-ppmu.c b/drivers/devfreq/event/exynos-ppmu.c
> index ad83473..5afb851 100644
> --- a/drivers/devfreq/event/exynos-ppmu.c
> +++ b/drivers/devfreq/event/exynos-ppmu.c
> @@ -354,7 +354,7 @@ static int exynos_ppmu_remove(struct platform_device *pdev)
> return 0;
> }
>
> -static struct of_device_id exynos_ppmu_id_match[] = {
> +static const struct of_device_id exynos_ppmu_id_match[] = {
> { .compatible = "samsung,exynos-ppmu", },
> { /* sentinel */ },
> };
> diff --git a/drivers/devfreq/tegra-devfreq.c b/drivers/devfreq/tegra-devfreq.c
> index 3479096..244d8db 100644
> --- a/drivers/devfreq/tegra-devfreq.c
> +++ b/drivers/devfreq/tegra-devfreq.c
> @@ -695,7 +695,7 @@ static SIMPLE_DEV_PM_OPS(tegra_devfreq_pm_ops,
> tegra_devfreq_suspend,
> tegra_devfreq_resume);
>
> -static struct of_device_id tegra_devfreq_of_match[] = {
> +static const struct of_device_id tegra_devfreq_of_match[] = {
> { .compatible = "nvidia,tegra124-actmon" },
> { },
> };
> --
> 2.1.0
>
>
next reply other threads:[~2015-03-17 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 1:11 MyungJoo Ham [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-16 19:17 [PATCH 00/35 linux-next] constify of_device_id array Fabian Frederick
[not found] ` <1426535685-25996-1-git-send-email-fabf@skynet.be>
[not found] ` <1426535685-25996-1-git-send-email-fabf-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>
2015-03-16 19:54 ` [PATCH 30/35 linux-next] devfreq: " Fabian Frederick
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=487895027.183321426554710978.JavaMail.weblogic@epmlwas07d \
--to=myungjoo.ham@samsung.com \
--cc=fabf@skynet.be \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).