From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752998AbbJNJ1b (ORCPT ); Wed, 14 Oct 2015 05:27:31 -0400 Received: from mail-ig0-f171.google.com ([209.85.213.171]:33780 "EHLO mail-ig0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751865AbbJNJ1R (ORCPT ); Wed, 14 Oct 2015 05:27:17 -0400 Date: Wed, 14 Oct 2015 17:26:53 +0800 From: Boqun Feng To: Peter Zijlstra 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: <20151014092653.GA29432@fixme-laptop.cn.ibm.com> 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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <20151014080613.GP17308@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 14, 2015 at 10:06:13AM +0200, Peter Zijlstra wrote: > On Wed, Oct 14, 2015 at 08:51:34AM +0800, Boqun Feng wrote: > > On Wed, Oct 14, 2015 at 11:10:00AM +1100, Michael Ellerman wrote: >=20 > > > Thanks for fixing this. In future you should send a patch like this a= s a > > > separate patch. I've not been paying attention to it because I assume= d it was > >=20 > > Got it. However, here is the thing, in previous version, this fix > > depends on some of other patches in this patchset. So to make this fix > > applied cleanly, I reorder my patchset to put this patch first, and the > > result is that some of other patches in this patchset depends on > > this(they need to remove code modified by this patch). > >=20 > > So I guess I'd better to stop Cc stable for this one, and wait until > > this patchset merged and send a separate patch for -stable tree. Does > > that work for you? I think this is what Peter want to suggests me to do > > when he asked me about this, right, Peter? >=20 > I don't think I had explicit thoughts about any of that, just that it > might make sense to have this patch not depend on the rest such that it > could indeed be stuffed into stable. >=20 Got that. Sorry for misunderstanding you... > I'll leave the details up to Michael since he's PPC maintainer. 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? Regards, Boqun --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWHh/ZAAoJEEl56MO1B/q4wbEIAI5iUUygtJPKne/zyMlmoGq3 MXynxxNc/blCstIn4Q7I9nIuoy6iXwefnN9TDnLGl/q9vcS4tl5/tnF6ktZglePI X4CXU1yjAb09nPi8mYWkwZT2QYu/AXlS3eJOtuKcZsG0v58475U8ilJnVeGmvMrt yJYMAT7qszuYQrW6LPX5OzbAcHzXoCQ5HepQq8G/dgpi37WFMxp35Qy6BC5Sh5AE 8PG323GsRP1KrCrkqEycgUX9i1pADZmcgv5HIuO4AO8b7WOF6M2s/PqQBL6v8YZt vSMwTSzg+S7Z5G5V34DthdUVhRzLvKwO0mFvOtK01ZJ1lRK3YzAJ1/qtUIYBjo0= =bPcE -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--