From: "zhangjianhua (E)" <chris.zjh@huawei.com>
To: <tglx@linutronix.de>, <peterz@infradead.org>,
<frederic@kernel.org>, <tannerlove@google.com>,
<edumazet@google.com>, <bigeasy@linutronix.de>,
<zouyipeng@huawei.com>, <liaochang1@huawei.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] genirq: Change irq_can_set_affinity() return value type to bool
Date: Wed, 24 Aug 2022 10:11:41 +0800 [thread overview]
Message-ID: <0dc95a9a-e801-aa7e-9075-4017a9cbb122@huawei.com> (raw)
In-Reply-To: <20220809124009.543646-1-chris.zjh@huawei.com>
kindly ping
在 2022/8/9 20:40, Zhang Jianhua 写道:
> The function irq_can_set_affinity() return from __irq_can_set_affinity()
> directly, whose return value type is bool, so make irq_can_set_affinity()
> return bool too.
>
> Signed-off-by: Zhang Jianhua <chris.zjh@huawei.com>
> ---
> include/linux/interrupt.h | 2 +-
> kernel/irq/manage.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
> index a92bce40b04b..29de49af6dea 100644
> --- a/include/linux/interrupt.h
> +++ b/include/linux/interrupt.h
> @@ -308,7 +308,7 @@ extern cpumask_var_t irq_default_affinity;
> extern int irq_set_affinity(unsigned int irq, const struct cpumask *cpumask);
> extern int irq_force_affinity(unsigned int irq, const struct cpumask *cpumask);
>
> -extern int irq_can_set_affinity(unsigned int irq);
> +extern bool irq_can_set_affinity(unsigned int irq);
> extern int irq_select_affinity(unsigned int irq);
>
> extern int __irq_apply_affinity_hint(unsigned int irq, const struct cpumask *m,
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index 40fe7806cc8c..dd9aeef68834 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -156,7 +156,7 @@ static bool __irq_can_set_affinity(struct irq_desc *desc)
> * @irq: Interrupt to check
> *
> */
> -int irq_can_set_affinity(unsigned int irq)
> +bool irq_can_set_affinity(unsigned int irq)
> {
> return __irq_can_set_affinity(irq_to_desc(irq));
> }
prev parent reply other threads:[~2022-08-24 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 12:40 Zhang Jianhua
2022-08-24 2:11 ` zhangjianhua (E) [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=0dc95a9a-e801-aa7e-9075-4017a9cbb122@huawei.com \
--to=chris.zjh@huawei.com \
--cc=bigeasy@linutronix.de \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tannerlove@google.com \
--cc=tglx@linutronix.de \
--cc=zouyipeng@huawei.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®