From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Hemant Kumar <hemant@linux.vnet.ibm.com>,
maddy@linux.vnet.ibm.com, srikar@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, warrier@linux.vnet.ibm.com,
paulus@samba.org, scottwood@freescale.com,
sukadev@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
mingo@kernel.org
Subject: Re: [PATCH v6 1/2] perf,kvm/powerpc: Add kvm_perf.h for powerpc
Date: Fri, 4 Sep 2015 17:51:45 -0300 [thread overview]
Message-ID: <20150904205145.GB3475@kernel.org> (raw)
In-Reply-To: <55E54A4F.6090205@linux.vnet.ibm.com>
Em Tue, Sep 01, 2015 at 12:18:47PM +0530, Hemant Kumar escreveu:
> >Should I try to process the 5 together, applying thest two first?
> Yes, this patchset needs to be applied before applying the other patchset,
> since there is a direct dependency on these two for the tooling part to
> work.
> >I see there are no acks from powerpc arch maintainers, how should we
> >proceed here? If there are no problems with the arch bits, and if it is
> >just to enable the tooling part, again, should I process the 5 as just
> >one series?
> The reason to split the earlier patchset into two was to separate the
> tooling/perf/ and arch/powerpc/ side patches, as asked by Michael..
> Here is the link to that discussion :
> http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg86916.html
> If Michael is ok with the patches, you can process all the 5 patches
> together. Michael?
Michael?
- Arnaldo
next prev parent reply other threads:[~2015-09-04 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:48 [PATCH v6 1/2] perf,kvm/powerpc: Add kvm_perf.h for powerpc Hemant Kumar
2015-08-31 6:48 ` [PATCH v6 2/2] perf,kvm/powerpc: Add hcall related info to kvm_perf.h Hemant Kumar
2015-08-31 20:13 ` [PATCH v6 1/2] perf,kvm/powerpc: Add kvm_perf.h for powerpc Arnaldo Carvalho de Melo
2015-09-01 6:48 ` Hemant Kumar
2015-09-04 20:51 ` Arnaldo Carvalho de Melo [this message]
2015-09-07 5:10 ` Michael Ellerman
2015-09-08 4:56 ` Hemant Kumar
2015-09-08 8:33 ` Michael Ellerman
2015-09-08 15:10 ` Arnaldo Carvalho de Melo
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=20150904205145.GB3475@kernel.org \
--to=acme@kernel.org \
--cc=hemant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=warrier@linux.vnet.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).