From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752965AbcGYPfs (ORCPT ); Mon, 25 Jul 2016 11:35:48 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34598 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751787AbcGYPfk (ORCPT ); Mon, 25 Jul 2016 11:35:40 -0400 Date: Mon, 25 Jul 2016 17:35:36 +0200 From: Ingo Molnar To: Stephen Rothwell Cc: Linus Torvalds , linux-kernel@vger.kernel.org, Peter Zijlstra , Arnaldo Carvalho de Melo , Jiri Olsa , Thomas Gleixner , Andrew Morton Subject: Re: [GIT PULL] perf changes for v4.8 Message-ID: <20160725153536.GA5715@gmail.com> References: <20160725082838.GA16210@gmail.com> <20160725235330.07c231a3@canb.auug.org.au> <20160725151520.GA5030@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160725151520.GA5030@gmail.com> 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 * Ingo Molnar wrote: > > * Stephen Rothwell wrote: > > > Hi Ingo, > > > > On Mon, 25 Jul 2016 10:28:38 +0200 Ingo Molnar wrote: > > > > > > tools: Copy the bitops files accessed from the kernel and check for drift > > > > I think this has some needs some fixes for build breakage in linux-next ... > > Only if combined with a single pending change from the luto-next tree, right? ... which commits come through the x86 tree, so there's no way for Linus to be exposed to that, right? That is why I sent this without mentioning the conflict. Is there any other complication that I missed? Thanks, Ingo