All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Thomas Klein <tklein@de.ibm.com>,
	pmac@au1.ibm.com, Jan-Bernd Themann <themann@de.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Christoph Raisch <raisch@de.ibm.com>,
	linux-ppc <linuxppc-dev@ozlabs.org>,
	Marcus Eder <meder@de.ibm.com>
Subject: Re: [PATCH 2.6.19-rc1] ehea firmware interface based on Anton	Blanchard's new hvcall interface
Date: Wed, 27 Sep 2006 18:30:02 -0400	[thread overview]
Message-ID: <451AFB6A.9010706@garzik.org> (raw)
In-Reply-To: <17690.63978.373862.727933@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:
> Jeff,
> 
>>> This eHEA patch reflects changes according to Anton's new hvcall interface
>>> which has been commited in Paul's git tree:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
>> When is this going upstream?  I don't want things to get too out-of-sync.
> 
> It's upstream already, and currently the ehea driver in Linus' tree
> doesn't compile as a result.

Thanks for the clarification.  The original quoted text sorta implied 
the opposite.

	Jeff

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff@garzik.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Jan-Bernd Themann <ossthema@de.ibm.com>,
	Thomas Klein <tklein@de.ibm.com>,
	Jan-Bernd Themann <themann@de.ibm.com>,
	pmac@au1.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ppc <linuxppc-dev@ozlabs.org>,
	Christoph Raisch <raisch@de.ibm.com>,
	Marcus Eder <meder@de.ibm.com>
Subject: Re: [PATCH 2.6.19-rc1] ehea firmware interface based on Anton	Blanchard's new hvcall interface
Date: Wed, 27 Sep 2006 18:30:02 -0400	[thread overview]
Message-ID: <451AFB6A.9010706@garzik.org> (raw)
In-Reply-To: <17690.63978.373862.727933@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:
> Jeff,
> 
>>> This eHEA patch reflects changes according to Anton's new hvcall interface
>>> which has been commited in Paul's git tree:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
>> When is this going upstream?  I don't want things to get too out-of-sync.
> 
> It's upstream already, and currently the ehea driver in Linus' tree
> doesn't compile as a result.

Thanks for the clarification.  The original quoted text sorta implied 
the opposite.

	Jeff




  reply	other threads:[~2006-09-27 22:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 16:47 [PATCH 2.6.19-rc1] ehea firmware interface based on Anton Blanchard's new hvcall interface Jan-Bernd Themann
2006-09-27 16:47 ` Jan-Bernd Themann
2006-09-27 21:52 ` Jeff Garzik
2006-09-27 21:52   ` Jeff Garzik
2006-09-27 22:23   ` Paul Mackerras
2006-09-27 22:23     ` Paul Mackerras
2006-09-27 22:30     ` Jeff Garzik [this message]
2006-09-27 22:30       ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2006-09-25 13:50 Jan-Bernd Themann
2006-09-25 13:50 ` Jan-Bernd Themann
2006-09-26  0:07 ` Jeff Garzik
2006-09-26  0:07   ` Jeff Garzik
2006-09-26  2:53   ` Benjamin Herrenschmidt
2006-09-26  2:53     ` 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=451AFB6A.9010706@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=meder@de.ibm.com \
    --cc=paulus@samba.org \
    --cc=pmac@au1.ibm.com \
    --cc=raisch@de.ibm.com \
    --cc=themann@de.ibm.com \
    --cc=tklein@de.ibm.com \
    /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.