mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "zhangjianhua (E)" <chris.zjh@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: <tglx@linutronix.de>, <samuel@sholland.org>, <brgl@bgdev.pl>,
	<mark.rutland@arm.com>, <lvjianmin@loongson.cn>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] genirq: Change can_request_irq() return value type to bool
Date: Fri, 16 Sep 2022 09:00:40 +0800	[thread overview]
Message-ID: <fff8db8f-7b8c-2050-2d95-50db0f2c033e@huawei.com> (raw)
In-Reply-To: <87wna6kvv5.wl-maz@kernel.org>

Fine, thanks.

在 2022/9/14 20:01, Marc Zyngier 写道:
> On Wed, 14 Sep 2022 12:06:15 +0100,
> Zhang Jianhua <chris.zjh@huawei.com> wrote:
>> The function can_request_irq() is used to judge whether the irq can be
>> allocated, so bool type would be more suitable for it.
>>
>> Signed-off-by: Zhang Jianhua <chris.zjh@huawei.com>
>> ---
>>   include/linux/irq.h | 2 +-
>>   kernel/irq/manage.c | 8 ++++----
>>   2 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/include/linux/irq.h b/include/linux/irq.h
>> index c3eb89606c2b..3a60c2313fb9 100644
>> --- a/include/linux/irq.h
>> +++ b/include/linux/irq.h
>> @@ -707,7 +707,7 @@ extern void note_interrupt(struct irq_desc *desc, irqreturn_t action_ret);
>>   extern int noirqdebug_setup(char *str);
>>   
>>   /* Checks whether the interrupt can be requested by request_irq(): */
>> -extern int can_request_irq(unsigned int irq, unsigned long irqflags);
>> +extern bool can_request_irq(unsigned int irq, unsigned long irqflags);
>>   
>>   /* Dummy irq-chip implementations: */
>>   extern struct irq_chip no_irq_chip;
>> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
>> index 40fe7806cc8c..d6940d15bf56 100644
>> --- a/kernel/irq/manage.c
>> +++ b/kernel/irq/manage.c
>> @@ -925,19 +925,19 @@ EXPORT_SYMBOL(irq_set_irq_wake);
>>    * particular irq has been exclusively allocated or is available
>>    * for driver use.
>>    */
>> -int can_request_irq(unsigned int irq, unsigned long irqflags)
>> +bool can_request_irq(unsigned int irq, unsigned long irqflags)
>>   {
>>   	unsigned long flags;
>>   	struct irq_desc *desc = irq_get_desc_lock(irq, &flags, 0);
>> -	int canrequest = 0;
>> +	bool canrequest = false;
>>   
>>   	if (!desc)
>> -		return 0;
>> +		return false;
>>   
>>   	if (irq_settings_can_request(desc)) {
>>   		if (!desc->action ||
>>   		    irqflags & desc->action->flags & IRQF_SHARED)
>> -			canrequest = 1;
>> +			canrequest = true;
>>   	}
>>   	irq_put_desc_unlock(desc, flags);
>>   	return canrequest;
> I'm sorry, but this is a very pointless change. Not only this doesn't
> change anything for this particular code other than being cosmetic,
> but it also doesn't help any of the callers which are still using an
> int.
>
> In general, this sort of patch only adds noise, and I'd like to see
> less of them.
>
> Thanks,
>
> 	M.
>

      reply	other threads:[~2022-09-16  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 11:06 Zhang Jianhua
2022-09-14 12:01 ` Marc Zyngier
2022-09-16  1:00   ` 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=fff8db8f-7b8c-2050-2d95-50db0f2c033e@huawei.com \
    --to=chris.zjh@huawei.com \
    --cc=brgl@bgdev.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvjianmin@loongson.cn \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=samuel@sholland.org \
    --cc=tglx@linutronix.de \
    /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®