From: Michael Ellerman <mpe@ellerman.id.au>
To: Alistair Popple <alistair@popple.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2 2/8] ipmi/powernv: Convert to irq event interface
Date: Mon, 27 Apr 2015 13:30:26 +1000 [thread overview]
Message-ID: <1430105426.8494.6.camel@ellerman.id.au> (raw)
In-Reply-To: <1428654294-9177-2-git-send-email-alistair@popple.id.au>
On Fri, 2015-04-10 at 18:24 +1000, Alistair Popple wrote:
> Convert the opal ipmi driver to use the new irq interface for events.
> drivers/char/ipmi/ipmi_powernv.c | 39 ++++++++++++++++++++++-----------------
This needs to be CC'ed to the IPMI folks, and preferably get their ACK so we
can take the whole series via the powerpc tree.
cheers
next prev parent reply other threads:[~2015-04-27 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 8:24 [PATCH V2 1/8] powerpc/powernv: Add a virtual irqchip for opal events Alistair Popple
2015-04-10 8:24 ` [PATCH V2 2/8] ipmi/powernv: Convert to irq event interface Alistair Popple
2015-04-27 3:30 ` Michael Ellerman [this message]
2015-04-10 8:24 ` [PATCH V2 3/8] hvc: Convert to using interrupts instead of opal events Alistair Popple
2015-04-10 8:24 ` [PATCH V2 4/8] powernv/eeh: Update the EEH code to use the opal irq domain Alistair Popple
2015-04-10 8:24 ` [PATCH V2 5/8] powernv/opal: Convert opal message events to " Alistair Popple
2015-04-10 8:24 ` [PATCH V2 6/8] powernv/elog: Convert elog " Alistair Popple
2015-04-10 8:24 ` [PATCH V2 7/8] powernv/opal-dump: Convert to " Alistair Popple
2015-04-10 8:24 ` [PATCH V2 8/8] opal: Remove events notifier Alistair Popple
2015-04-30 18:30 ` [PATCH V2 1/8] powerpc/powernv: Add a virtual irqchip for opal events Neelesh Gupta
2015-04-30 18:44 ` Neelesh Gupta
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=1430105426.8494.6.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=alistair@popple.id.au \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).