From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
henrix@sapo.pt, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:irq/genirq] genirq: do not execute DEBUG_SHIRQ when irq setup failed
Date: Thu, 02 Apr 2009 21:11:44 +0530 [thread overview]
Message-ID: <1238686904.3099.22.camel@ht.satnam> (raw)
In-Reply-To: <alpine.LFD.2.00.0904021718230.12916@localhost.localdomain>
On Thu, 2009-04-02 at 17:21 +0200, Thomas Gleixner wrote:
> On Thu, 2 Apr 2009, Jaswinder Singh Rajput wrote:
> > On Thu, 2009-04-02 at 14:03 +0000, Luis Henriques wrote:
> > > Commit-ID: ba71604fad348656071a2a76eef9a67dab85a773
> > > Gitweb: http://git.kernel.org/tip/ba71604fad348656071a2a76eef9a67dab85a773
> > > Author: Luis Henriques <henrix@sapo.pt>
> > > AuthorDate: Wed, 1 Apr 2009 18:06:35 +0100
> > > Committer: Thomas Gleixner <tglx@linutronix.de>
> > > CommitDate: Thu, 2 Apr 2009 16:02:39 +0200
> > >
> > > genirq: do not execute DEBUG_SHIRQ when irq setup failed
> > >
> > > When requesting an IRQ, the DEBUG_SHIRQ code executes a fake IRQ just to make
> > > sure the driver is ready to receive an IRQ immediately. The problem was that
> > > this fake IRQ was being executed even if interrupt line failed to be allocated
> > > by __setup_irq.
> > >
> > > Signed-off-by: Luis Henriques <henrix@sapo.pt>
> > > LKML-Reference: <20090401170635.GA4392@hades.domain.com>
> > > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > >
> > >
> > > ---
> > > kernel/irq/manage.c | 2 +-
> > > 1 files changed, 1 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> > > index 1516ab7..beeb7d1 100644
> > > --- a/kernel/irq/manage.c
> > > +++ b/kernel/irq/manage.c
> > > @@ -768,7 +768,7 @@ int request_irq(unsigned int irq, irq_handler_t handler,
> > > kfree(action);
> > >
> > > #ifdef CONFIG_DEBUG_SHIRQ
> > > - if (irqflags & IRQF_SHARED) {
> > > + if (!retval & (irqflags & IRQF_SHARED)) {
> > > /*
> > > * It's a shared IRQ -- the driver ought to be prepared for it
> > > * to happen immediately, so let's make sure....
> >
> > What is this ?
>
> You looking at the wrong place.
>
> > There is no retval:
> >
> > http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=blob;f=kernel/irq/manage.c;h=a3eb7baf1e46f2c735edb4cc44e0386cfbc4989e;hb=HEAD
>
> Care to read patches you want to comment on carefully _BEFORE_ you
> start yelling at people and sending useless copies of the wrong
> function around the world.
>
> The patch is perfectly fine and already applied.
>
Yes, I know somehow you applied it. When you will merge this branch with
-tip/master then you will understand what I am saying.
Even function name is changed from:
713 int request_irq(unsigned int irq, irq_handler_t handler,
714
unsigned long irqflags, const char *devname, void *dev_id)
715 {
716 struct irqaction *action;
717 struct irq_desc *desc;
718 int retval;
to:
857 int request_threaded_irq(unsigned int irq, irq_handler_t handler,
858
irq_handler_t thread_fn, unsigned long irqflags,
859 const char *devname, void *dev_id)
860 {
861 struct irqaction *action;
862 struct irq_desc *desc;
863 int retval;
--
JSR
next prev parent reply other threads:[~2009-04-02 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 17:06 [RESEND][PATCH -tip] irq: DEBUG_SHIRQ executed on irq setup failure Luis Henriques
2009-04-02 14:03 ` [tip:irq/genirq] genirq: do not execute DEBUG_SHIRQ when irq setup failed Luis Henriques
2009-04-02 14:32 ` Jaswinder Singh Rajput
2009-04-02 15:21 ` Thomas Gleixner
2009-04-02 15:41 ` Jaswinder Singh Rajput [this message]
2009-04-02 16:08 ` Thomas Gleixner
2009-04-02 16:20 ` Jaswinder Singh Rajput
2009-04-02 16:38 ` Thomas Gleixner
2009-04-02 16:45 ` Jaswinder Singh Rajput
2009-04-02 17:16 ` Luis Henriques
2009-04-02 17:32 ` Ingo Molnar
2009-04-02 17:46 ` Jaswinder Singh Rajput
2009-04-02 18:01 ` Ingo Molnar
2009-04-23 6:48 ` tip-bot for Luis Henriques
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=1238686904.3099.22.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=henrix@sapo.pt \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--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®