From: Jeremy Kerr <jk@ozlabs.org>
To: minyard@acm.org, linuxppc-dev@lists.ozlabs.org,
openipmi-developer@lists.sourceforge.net
Cc: Michael Ellerman <michael@ellerman.id.au>
Subject: Re: [PATCH v2] drivers/char/ipmi: Add powernv IPMI driver
Date: Fri, 14 Nov 2014 10:00:47 +0800 [thread overview]
Message-ID: <5465624F.6010605@ozlabs.org> (raw)
In-Reply-To: <54655DFE.6080503@acm.org>
Hi Corey,
> This looks good. Can this go into the IPMI tree now, or does it need
> work done in the PowerPC tree first?
The 1/2 patch is already in the powerpc tree - but to ensure that we hit
Linus' tree in the right order, Michael has suggested that you merge his
topic branch (which only has that one change):
https://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/log/?h=topic/opal-ipmi
- then apply the patch. This way, whichever tree Linus pulls first will
have the changes in the correct order.
Cheers,
Jeremy
next prev parent reply other threads:[~2014-11-14 2:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 3:38 [PATCH 0/2] Add IPMI support for powernv powerpc machines Jeremy Kerr
2014-11-06 3:38 ` [PATCH 1/2] powerpc/powernv: Add OPAL IPMI interface Jeremy Kerr
2014-11-06 3:38 ` [PATCH 2/2] drivers/char/ipmi: Add powernv IPMI driver Jeremy Kerr
2014-11-06 14:15 ` [PATCH 0/2] Add IPMI support for powernv powerpc machines Corey Minyard
2014-11-10 3:26 ` Jeremy Kerr
2014-11-10 5:41 ` Benjamin Herrenschmidt
2014-11-10 6:01 ` Alistair Popple
2014-11-10 6:57 ` Benjamin Herrenschmidt
2014-11-10 6:41 ` Jeremy Kerr
2014-11-11 21:07 ` Corey Minyard
2014-11-12 6:10 ` Michael Ellerman
2014-11-12 7:37 ` Jeremy Kerr
2014-11-12 7:41 ` [PATCH v2] drivers/char/ipmi: Add powernv IPMI driver Jeremy Kerr
2014-11-14 1:42 ` Corey Minyard
2014-11-14 2:00 ` Jeremy Kerr [this message]
2014-11-14 2:04 ` Michael Ellerman
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=5465624F.6010605@ozlabs.org \
--to=jk@ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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.