From: Ingo Molnar <mingo@elte.hu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
Yinghai Lu <yinghai@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Bug in "genirq: record trigger type"
Date: Tue, 21 Oct 2008 09:33:50 +0200 [thread overview]
Message-ID: <20081021073350.GA22351@elte.hu> (raw)
In-Reply-To: <1224574343.7654.244.camel@pasglop>
* Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Tue, 2008-10-21 at 09:28 +0200, Ingo Molnar wrote:
>
> > From: Chris Friesen <cfriesen@nortel.com>
> > Date: Mon, 20 Oct 2008 12:41:58 -0600
> > Subject: [PATCH] genirq: fix set_irq_type() when recording trigger type
> >
> > In set_irq_type() we want to pass the type rather than the current
> > interrupt state.
> >
> > Signed-off-by: Chris Friesen <cfriesen@nortel.com>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
thx, added your ack to the commit as well.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Brownell <dbrownell@users.sourceforge.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Bug in "genirq: record trigger type"
Date: Tue, 21 Oct 2008 09:33:50 +0200 [thread overview]
Message-ID: <20081021073350.GA22351@elte.hu> (raw)
In-Reply-To: <1224574343.7654.244.camel@pasglop>
* Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Tue, 2008-10-21 at 09:28 +0200, Ingo Molnar wrote:
>
> > From: Chris Friesen <cfriesen@nortel.com>
> > Date: Mon, 20 Oct 2008 12:41:58 -0600
> > Subject: [PATCH] genirq: fix set_irq_type() when recording trigger type
> >
> > In set_irq_type() we want to pass the type rather than the current
> > interrupt state.
> >
> > Signed-off-by: Chris Friesen <cfriesen@nortel.com>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
thx, added your ack to the commit as well.
Ingo
next prev parent reply other threads:[~2008-10-21 7:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810202205.m9KM5une024759@hera.kernel.org>
2008-10-21 6:32 ` Bug in "genirq: record trigger type" Benjamin Herrenschmidt
2008-10-21 6:32 ` Benjamin Herrenschmidt
2008-10-21 7:22 ` Yinghai Lu
2008-10-21 7:22 ` Yinghai Lu
2008-10-21 7:28 ` Ingo Molnar
2008-10-21 7:28 ` Ingo Molnar
2008-10-21 7:32 ` Benjamin Herrenschmidt
2008-10-21 7:32 ` Benjamin Herrenschmidt
2008-10-21 7:33 ` Ingo Molnar [this message]
2008-10-21 7:33 ` Ingo Molnar
2008-10-21 7:23 ` [PATCH] genirq: fix set_irq_type() when recording trigger type Ingo Molnar
2008-10-21 7:23 ` Ingo Molnar
2008-10-21 8:01 ` Bug in "genirq: record trigger type" David Brownell
2008-10-21 8:01 ` David Brownell
2008-10-21 8:29 ` Benjamin Herrenschmidt
2008-10-21 8:29 ` Benjamin Herrenschmidt
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=20081021073350.GA22351@elte.hu \
--to=mingo@elte.hu \
--cc=benh@kernel.crashing.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.