From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932112AbdEJWyB (ORCPT ); Wed, 10 May 2017 18:54:01 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:35192 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753902AbdEJWyA (ORCPT ); Wed, 10 May 2017 18:54:00 -0400 Date: Wed, 10 May 2017 15:53:57 -0700 From: "Paul E. McKenney" To: Linus Torvalds Cc: Ingo Molnar , Linux Kernel Mailing List , Peter Zijlstra , Thomas Gleixner Subject: Re: [RFC GIT PULL, v2] RCU changes for v4.12 Reply-To: paulmck@linux.vnet.ibm.com References: <20170501095915.rm4zi5z4ta44il5p@gmail.com> <20170509072640.sbvhtjy7mcw7ndo3@gmail.com> <20170510195440.GW3956@linux.vnet.ibm.com> <20170510205109.GX3956@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 x-cbid: 17051022-2213-0000-0000-000001B42F2E X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00007044; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000210; SDB=6.00858859; UDB=6.00425603; IPR=6.00638335; BA=6.00005342; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015403; XFM=3.00000015; UTC=2017-05-10 22:53:58 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17051022-2214-0000-0000-0000561149FB Message-Id: <20170510225357.GZ3956@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-05-10_19:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705100155 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 10, 2017 at 02:08:55PM -0700, Linus Torvalds wrote: > On Wed, May 10, 2017 at 1:51 PM, Paul E. McKenney > wrote: > > On Wed, May 10, 2017 at 01:17:54PM -0700, Linus Torvalds wrote: > >> > >> It kind of implies that the prep work that linux-next does doesn't get > >> fully used. > > > > I did see that from linux-next. For future reference, what should I > > have done with it? Added it to my pull request or to the commit log of > > my merge commit? > > Basically, just forward the information along with the description of > what's in the branch, so that I know to expect it. > > In this case it didn't actually *matter*, since I noticed it on my > own, but particularly if I'm on the road I don't generally have the > compute power with me to do a full allmodconfig build between each > pull (I usually do one or two a day), so I can miss these things more > easily. And if it happens on other architectures, I wouldn't notice. > > It doesn't have to be exhaustive. Just a note saying that "there's > going to be a semantic merge conflict in file xyz due to abc" means > that I can then specifically take it into account. Even if I were to > be on the road, I can then check that particular driver out and make > sure to check that it builds, etc. Got it, thank you! > [ Sometimes I also take those kinds of conflict notes into account for > pull scheduling. For example, back when the kids were small, and I > ended up having to occasionally drive them around, I used to aim to do > the simple quick pulls first, delaying things that might need more > care until I didn't have some driving schedule over my head. That > happens less these days when the kids are off to college and the sole > remaining one mostly drives herself around. ] Time does fly -- my youngest graduated from college a couple of years ago. Thanx, Paul