From: Jeff Garzik <jgarzik@pobox.com>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: Robert Jennings <rcj@linux.vnet.ibm.com>,
paulus@samba.org, linuxppc-dev@ozlabs.org,
netdev@vger.kernel.org, Santiago Leon <santil@us.ibm.com>,
Nathan Fontenot <nfont@austin.ibm.com>,
David Darrington <ddarring@linux.vnet.ibm.com>
Subject: Re: [PATCH 10/19] [repost] powerpc: move get_longbusy_msecs out of ehca/ehea
Date: Fri, 13 Jun 2008 15:55:41 -0400 [thread overview]
Message-ID: <4852D0BD.7010403@pobox.com> (raw)
In-Reply-To: <4852BB43.9080305@linux.vnet.ibm.com>
Brian King wrote:
> Jeff,
>
> Regarding the patches Rob just posted here, we'd like to just take them
> through the powerpc tree with your sign off since they are part of a
> Power platform feature we are enabling.
>
> Thanks,
>
> Brian
>
> Robert Jennings wrote:
>> From: Robert Jennings <rcj@linux.vnet.ibm.com>
>>
>> In support of Cooperative Memory Overcommitment (CMO) this moves
>> get_longbusy_msecs() out of the ehca and ehea drivers and into the
>> architecture's hvcall header as plpar_get_longbusy_msecs. Some firmware
>> calls made in pSeries platform iommu code will need to share this
>> functionality.
>>
>> Signed-off-by: Robert Jennings <rcj@linux.vnet.ibm.com>
>>
>> ---
>>
>> I missed copying netdev on this patch the first time.
>>
>> drivers/infiniband/hw/ehca/hcp_if.c | 24 ++----------------------
>> drivers/net/ehea/ehea_phyp.c | 4 ++--
>> drivers/net/ehea/ehea_phyp.h | 20 --------------------
>> include/asm-powerpc/hvcall.h | 27 +++++++++++++++++++++++++++
>> 4 files changed, 31 insertions(+), 44 deletions(-)
ACK the quoted patch
prev parent reply other threads:[~2008-06-13 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080612221535.GQ30916@linux.vnet.ibm.com>
2008-06-12 22:18 ` [PATCH 10/19] [repost] powerpc: move get_longbusy_msecs out of ehca/ehea Robert Jennings
2008-06-13 18:24 ` Brian King
2008-06-13 19:55 ` Jeff Garzik [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=4852D0BD.7010403@pobox.com \
--to=jgarzik@pobox.com \
--cc=brking@linux.vnet.ibm.com \
--cc=ddarring@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=nfont@austin.ibm.com \
--cc=paulus@samba.org \
--cc=rcj@linux.vnet.ibm.com \
--cc=santil@us.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 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).