From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753498AbcAYGFW (ORCPT ); Mon, 25 Jan 2016 01:05:22 -0500 Received: from e36.co.us.ibm.com ([32.97.110.154]:60527 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751031AbcAYGFS (ORCPT ); Mon, 25 Jan 2016 01:05:18 -0500 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Sun, 24 Jan 2016 22:05:11 -0800 From: "Paul E. McKenney" To: "Huang, Ying" Cc: Davidlohr Bueso , Waiman Long , Peter Zijlstra , lkp@01.org, Will Deacon , LKML , Linus Torvalds , Ingo Molnar , Ding Tianhong , Thomas Gleixner , fengguang.wu@intel.com, Tim Chen , Jason Low Subject: Re: [LKP] [lkp] [locking/mutexes] cb4bbc457b: -40.0% unixbench.score Message-ID: <20160125060511.GE4503@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <874me6jql0.fsf@yhuang-dev.intel.com> <20160122024801.GA23224@linux-uzut.site> <87io2iih8w.fsf@yhuang-dev.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87io2iih8w.fsf@yhuang-dev.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16012506-0021-0000-0000-00001666A32C Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 25, 2016 at 09:23:59AM +0800, Huang, Ying wrote: > Davidlohr Bueso writes: > > > On Fri, 22 Jan 2016, kernel test robot wrote: > > > >>FYI, we noticed the below changes on > >> > >>https://github.com/0day-ci/linux > >> Ding-Tianhong/locking-mutexes-don-t-spin-on-owner-when-wait-list-is-not-NULL/20160121-173317 > >>commit cb4bbc457bfed6194ffab1b10c7be73b3f16ca2d ("locking/mutexes: don't spin on owner when wait list is not NULL.") > > > > I'm not sure why this would even be reported, as this patch has not been accepted > > or acked or nothin', by anyone. > > Sorry for bothering. The purpose is FYI as in the original report > email. We test patches posted to LKML, if we found some changes related > to the patch, we will send out a report. Hope the reviewer could > take that as information for his/her review if the report isn't totally > nonsense. For me, the 0day reports on LKML postings have been quite helpful. They give the submitter immediate feedback on a number of issues, thus reducing the number of rounds of review. Thanx, Paul