From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] powerpc: export cpu_to_core_id()
Date: Thu, 2 Jun 2016 08:22:11 -0300 [thread overview]
Message-ID: <201606021122.u52BLbJF015655@mx0a-001b2d01.pphosted.com> (raw)
In-Reply-To: <1464865393.11826.0.camel@ellerman.id.au>
On 06/02/2016 08:03 AM, Michael Ellerman wrote:
> Can you send me a v2 with a change log that includes all that detail.
Sure; should have done it. Thanks.
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
prev parent reply other threads:[~2016-06-02 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 20:16 [PATCH 1/3] powerpc: export cpu_to_core_id() Mauricio Faria de Oliveira
2016-06-01 20:19 ` Mauricio Faria de Oliveira
2016-06-02 7:41 ` Michael Ellerman
2016-06-02 9:00 ` Mauricio Faria de Oliveira
2016-06-02 9:05 ` Mauricio Faria de Oliveira
[not found] ` <201606020900.u528tQHH025445@mx0a-001b2d01.pphosted.com>
2016-06-02 11:03 ` Michael Ellerman
2016-06-02 11:22 ` 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=201606021122.u52BLbJF015655@mx0a-001b2d01.pphosted.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).