From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Michael Ellerman <michaele@au1.ibm.com>,
tglx@linutronix.de, kvm@vger.kernel.org, oleg@redhat.com,
peterz@infradead.org, fweisbec@gmail.com, bobby.prani@gmail.com,
jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
kvm-ppc@vger.kernel.org, josh@joshtriplett.org,
dhowells@redhat.com, edumazet@google.com,
"paulus@samba.org" <paulus@samba.org>,
rostedt@goodmis.org, dipankar@in.ibm.com,
mathieu.desnoyers@efficios.com, akpm@linux-foundation.org,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
mingo@kernel.org
Subject: Re: powerpc KVM build break in linux-next (was Re: [PATCH tip/core/rcu 40/40] srcu: Parallelize callback handling)
Date: Fri, 21 Apr 2017 05:51:35 -0700 [thread overview]
Message-ID: <20170421125135.GW3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <ca07b47e-8141-1691-169d-16c99d03902a@redhat.com>
On Fri, Apr 21, 2017 at 09:27:59AM +0200, Paolo Bonzini wrote:
>
>
> On 21/04/2017 06:17, Paul E. McKenney wrote:
> >> Thanks, this looks perfect to me, and if you're happy to put it on top
> >> of your tree that would limit the breakage to a smaller history window,
> >> so that would be ideal.
> >>
> >> Tested-by: Michael Ellerman <mpe@ellerman.id.au>
> > Thank you, Michael!
> >
> > Paolo, does this look good to you? My upstream maintainer will be much
> > more likely to take this with your ack. ;-)
>
> Sure,
>
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>
> since I don't expect conflicts between whoever applies this patch and
> the KVM tree.
Applied, thank you!
Thanx, Paul
next prev parent reply other threads:[~2017-04-21 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170412174003.GA23207@linux.vnet.ibm.com>
2017-04-12 17:39 ` [PATCH tip/core/rcu 02/40] rcu: Make arch select smp_mb__after_unlock_lock() strength Paul E. McKenney
2017-04-13 9:21 ` Peter Zijlstra
2017-04-13 16:17 ` Paul E. McKenney
2017-04-13 9:24 ` Peter Zijlstra
2017-04-13 16:26 ` Paul E. McKenney
2017-04-13 16:37 ` Peter Zijlstra
2017-04-13 17:03 ` Paul E. McKenney
2017-04-19 13:38 ` Michael Ellerman
2017-04-19 15:09 ` Paul E. McKenney
[not found] ` <1492018825-25634-40-git-send-email-paulmck@linux.vnet.ibm.com>
2017-04-20 3:40 ` powerpc KVM build break in linux-next (was Re: [PATCH tip/core/rcu 40/40] srcu: Parallelize callback handling) Michael Ellerman
2017-04-20 14:19 ` Paul E. McKenney
2017-04-20 15:28 ` Paolo Bonzini
2017-04-21 0:38 ` Paul E. McKenney
2017-04-21 1:42 ` Michael Ellerman
2017-04-21 4:17 ` Paul E. McKenney
2017-04-21 7:27 ` Paolo Bonzini
2017-04-21 12:51 ` Paul E. McKenney [this message]
2017-04-22 6:09 ` Michael Ellerman
2017-04-21 2:13 ` Michael Ellerman
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=20170421125135.GW3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=michaele@au1.ibm.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).