From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: anish kumar <anish198519851985@gmail.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
akpm@linux-foundation.org, paul.gortmaker@windriver.com,
mingo@kernel.org, fweisbec@gmail.com
Subject: Re: [PATCH] IRQ CORE: irq_work_queue function return value not used.
Date: Fri, 2 Nov 2012 22:49:45 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1211022249150.2756@ionos> (raw)
In-Reply-To: <1351863814.4004.126.camel@gandalf.local.home>
On Fri, 2 Nov 2012, Steven Rostedt wrote:
> On Fri, 2012-11-02 at 22:24 +0900, anish kumar wrote:
> > From: anish kumar <anish198519851985@gmail.com>
> >
> > As no one is using the return value of irq_work_queue function
> > it is better to just make it void.
>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
>
> Peter, like to take this patch? Or is there a reason you have for
> irq_work_queue() returning a value?
>
> -- Steve
>
> > Signed-off-by: anish kumar <anish198519851985@gmail.com>
> > ---
> > kernel/irq_work.c | 6 +++---
> > 1 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/kernel/irq_work.c b/kernel/irq_work.c
> > index 1588e3b..a85c4b3 100644
> > --- a/kernel/irq_work.c
> > +++ b/kernel/irq_work.c
> > @@ -79,17 +79,17 @@ static void __irq_work_queue(struct irq_work *work)
> > *
> > * Can be re-enqueued while the callback is still in progress.
> > */
> > -bool irq_work_queue(struct irq_work *work)
> > +void irq_work_queue(struct irq_work *work)
> > {
> > if (!irq_work_claim(work)) {
> > /*
> > * Already enqueued, can't do!
> > */
> > - return false;
> > + return;
> > }
> >
> > __irq_work_queue(work);
> > - return true;
> > + return;
And while at it please zap that pointless "return;" statement.
> > }
> > EXPORT_SYMBOL_GPL(irq_work_queue);
> >
>
>
>
next prev parent reply other threads:[~2012-11-02 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 13:24 [PATCH] IRQ CORE: irq_work_queue function return value not used anish kumar
2012-11-02 13:43 ` Steven Rostedt
2012-11-02 21:49 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-03 8:57 anish kumar
2013-01-26 16:24 ` Frederic Weisbecker
2013-02-02 3:14 ` anish kumar
2013-02-02 4:33 ` Frederic Weisbecker
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=alpine.LFD.2.02.1211022249150.2756@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=anish198519851985@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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