From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: james.smart@broadcom.com, dick.kennedy@broadcom.com
Subject: Re: [PATCH 0/2] lpfc: PowerPC64 topology information, and per-core scheduling
Date: Tue, 21 Jun 2016 10:42:12 -0300 [thread overview]
Message-ID: <57694434.1010606@linux.vnet.ibm.com> (raw)
In-Reply-To: <201606012043.u51KdPlB044752@mx0a-001b2d01.pphosted.com>
On 06/01/2016 05:43 PM, Mauricio Faria de Oliveira wrote:
> Tested on next-20160601 (with an extra commit for patch 1/2, see commit msg).
FYI, that commit has been accepted into powerpc next [1].
[1] https://git.kernel.org/powerpc/c/f8ab481066e7246e4b272233aa
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
prev parent reply other threads:[~2016-06-21 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 20:43 [PATCH 0/2] lpfc: PowerPC64 topology information, and per-core scheduling Mauricio Faria de Oliveira
2016-06-21 13:42 ` Mauricio Faria de Oliveira [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=57694434.1010606@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=linux-scsi@vger.kernel.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).