From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752905AbbJNJdZ (ORCPT ); Wed, 14 Oct 2015 05:33:25 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:46396 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751257AbbJNJdX (ORCPT ); Wed, 14 Oct 2015 05:33:23 -0400 Date: Wed, 14 Oct 2015 11:33:07 +0200 From: Peter Zijlstra To: Boqun Feng Cc: Michael Ellerman , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Ingo Molnar , Benjamin Herrenschmidt , Paul Mackerras , Thomas Gleixner , Will Deacon , "Paul E. McKenney" , Waiman Long , Davidlohr Bueso , stable@vger.kernel.org Subject: Re: [PATCH RESEND v3 1/6] powerpc: atomic: Make *xchg and *cmpxchg a full barrier Message-ID: <20151014093307.GC3816@twins.programming.kicks-ass.net> References: <1444659246-24769-1-git-send-email-boqun.feng@gmail.com> <1444660220-25559-1-git-send-email-boqun.feng@gmail.com> <1444781400.12197.4.camel@ellerman.id.au> <20151014005134.GE23991@fixme-laptop.cn.ibm.com> <20151014080613.GP17308@twins.programming.kicks-ass.net> <20151014092653.GA29432@fixme-laptop.cn.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151014092653.GA29432@fixme-laptop.cn.ibm.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 14, 2015 at 05:26:53PM +0800, Boqun Feng wrote: > Michael and Peter, rest of this patchset depends on commits which are > currently in the locking/core branch of the tip, so I would like it as a > whole queued there. Besides, I will keep this patch Cc'ed to stable in > future versions, that works for you both? >>From my POV having the Cc stable in there is fine if Michael actually wants them to go there. GregKH will vacuum them up once they hit Linus' tree and we don't need to think about it anymore. Alternatively, Michael could put the patch in a separate branch and we could both merge that. Or even, seeing how its a single patch and git mostly does the right thing, we could just merge it independently in both trees and let git sort it out at merge time.