From: Angus Chen <angus.chen@jaguarmicro.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] genirq: Remove unused parameter force of irq_set_affinity_deactivated()
Date: Sat, 12 Nov 2022 02:06:43 +0000 [thread overview]
Message-ID: <TY2PR06MB34244F5E7353682050F6B90785039@TY2PR06MB3424.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <87cz9tcqg5.ffs@tglx>
Hi tglx.
> -----Original Message-----
> From: Thomas Gleixner <tglx@linutronix.de>
> Sent: Saturday, November 12, 2022 2:11 AM
> To: Angus Chen <angus.chen@jaguarmicro.com>
> Cc: linux-kernel@vger.kernel.org; Angus Chen <angus.chen@jaguarmicro.com>
> Subject: Re: [PATCH] genirq: Remove unused parameter force of
> irq_set_affinity_deactivated()
>
> On Fri, Oct 07 2022 at 18:32, Angus Chen wrote:
> > The force parameter in irq_set_affinity_deactivated() is not used,
> > get rid of it.
>
> Correct.
>
> > Fixes: baedb87d1b53 ("genirq/affinity: Handle affinity setting on
> > inactive interrupts correctly")
>
> What does this fix? An unused argument is neither a bug nor a
> problem. Removing it is a cleanup nothing else.
>
Thank you for your reply.
I almost forget this patch because it just a cleanup.
I thought maybe it is too simple to submit,
so it be ignored by maintainer.
Can I send a v2 to modify the git log ?
Thanks.
> Thanks,
>
> tglx
next prev parent reply other threads:[~2022-11-12 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 10:32 [PATCH] genirq: Remove unused parameter force of irq_set_affinity_deactivated() Angus Chen
2022-11-11 18:10 ` Thomas Gleixner
2022-11-12 2:06 ` Angus Chen [this message]
2022-11-17 15:08 ` [tip: irq/core] genirq: Remove unused argument " tip-bot2 for Angus Chen
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=TY2PR06MB34244F5E7353682050F6B90785039@TY2PR06MB3424.apcprd06.prod.outlook.com \
--to=angus.chen@jaguarmicro.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).