From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Hailong Liu <liuhailongg6@163.com>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-mips@vger.kernel.org, Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hailong Liu <liu.hailong6@zte.com.cn>
Subject: Re: [PATCH] CPUFREQ: loongson2: Remove unused linux/sched.h headers
Date: Mon, 7 Jun 2021 17:48:06 +0200 [thread overview]
Message-ID: <CAJZ5v0he09ttX-EnXukHcqk4okdp1ag7dEH3BQQ_AsPOMMOBpg@mail.gmail.com> (raw)
In-Reply-To: <20210604034709.kxqy6vcfvtxf5rje@vireshk-i7>
On Fri, Jun 4, 2021 at 5:48 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 03-06-21, 21:57, Hailong Liu wrote:
> > From: Hailong Liu <liu.hailong6@zte.com.cn>
> >
> > Since commit 759f534e93ac(CPUFREQ: Loongson2: drop set_cpus_allowed_ptr()),
> > the header <linux/sched.h> is useless in oongson2_cpufreq.c, so remove it.
> >
> > Signed-off-by: Hailong Liu <liu.hailong6@zte.com.cn>
> > ---
> > drivers/cpufreq/loongson2_cpufreq.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/loongson2_cpufreq.c b/drivers/cpufreq/loongson2_cpufreq.c
> > index d05e761d9572..afc59b292153 100644
> > --- a/drivers/cpufreq/loongson2_cpufreq.c
> > +++ b/drivers/cpufreq/loongson2_cpufreq.c
> > @@ -16,7 +16,6 @@
> > #include <linux/cpufreq.h>
> > #include <linux/module.h>
> > #include <linux/err.h>
> > -#include <linux/sched.h> /* set_cpus_allowed() */
> > #include <linux/delay.h>
> > #include <linux/platform_device.h>
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied as 5.14 material, thanks!
prev parent reply other threads:[~2021-06-07 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 13:57 [PATCH] CPUFREQ: loongson2: Remove unused linux/sched.h headers Hailong Liu
2021-06-04 3:47 ` Viresh Kumar
2021-06-07 15:48 ` Rafael J. Wysocki [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=CAJZ5v0he09ttX-EnXukHcqk4okdp1ag7dEH3BQQ_AsPOMMOBpg@mail.gmail.com \
--to=rafael@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=liu.hailong6@zte.com.cn \
--cc=liuhailongg6@163.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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).