From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753830AbbIJAna (ORCPT ); Wed, 9 Sep 2015 20:43:30 -0400 Received: from ozlabs.org ([103.22.144.67]:54947 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751829AbbIJAn0 (ORCPT ); Wed, 9 Sep 2015 20:43:26 -0400 Message-ID: <1441845803.31931.0.camel@ellerman.id.au> Subject: Re: [[PATCH v6 09/10] powerpc/perf/hv-24x7: Use PMU_TXN_READ interface From: Michael Ellerman To: Sukadev Bhattiprolu Cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, sparclinux@vger.kernel.org Date: Thu, 10 Sep 2015 10:43:23 +1000 In-Reply-To: <20150909211255.GB30739@us.ibm.com> References: <1441336073-22750-1-git-send-email-sukadev@linux.vnet.ibm.com> <1441336073-22750-10-git-send-email-sukadev@linux.vnet.ibm.com> <1441703275.7601.5.camel@ellerman.id.au> <20150908112900.GF3644@twins.programming.kicks-ass.net> <1441764905.7854.5.camel@ellerman.id.au> <20150909211255.GB30739@us.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2015-09-09 at 14:12 -0700, Sukadev Bhattiprolu wrote: > Michael Ellerman [mpe@ellerman.id.au] wrote: > | > > This looks fine to me from an arch perspective. I assume the whole series can > | > > go via tip-something? > | > > | > Yeah, I've had it queued for a few days, there was one s390 compile > | > fail reported by the build-bot, which I've just fixed. So if nothing > | > weird happens, it should hit tip somewhere this week. > > Peter, thanks for fixing the typo. > > | > | Great, thanks. > | > | Now Sukadev can focus on getting the JSON events support merged, hopefully it > | won't require another 16 versions. > > :-) BTW, other than an occasional patch from Andi Kleen (on top of the v16), I > have not received any comments on the JSON file patch set, so I don't have a > v17 in the pipeline... Yeah. I assume everyone's happy with it and someone is going to pick it up for the next merge window? cheers