linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: minyard@acm.org
Cc: openipmi-developer@lists.sourceforge.net,
	linuxppc-dev@lists.ozlabs.org, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH v2] drivers/char/ipmi: Add powernv IPMI driver
Date: Fri, 14 Nov 2014 13:04:51 +1100	[thread overview]
Message-ID: <1415930691.26378.1.camel@concordia> (raw)
In-Reply-To: <54655DFE.6080503@acm.org>

On Thu, 2014-11-13 at 19:42 -0600, Corey Minyard wrote:
> This looks good.  Can this go into the IPMI tree now, or does it need
> work done in the PowerPC tree first?

You need to merge this first:

  https://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/log/?h=topic/opal-ipmi

ie.

  $ git fetch git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git topic/opal-ipmi
  $ git merge FETCH_HEAD

cheers

      parent reply	other threads:[~2014-11-14  2:04 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
2014-11-14  2:04         ` Michael Ellerman [this message]

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=1415930691.26378.1.camel@concordia \
    --to=mpe@ellerman.id.au \
    --cc=jk@ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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 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).