From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753745AbdBGLSr (ORCPT ); Tue, 7 Feb 2017 06:18:47 -0500 Received: from ozlabs.org ([103.22.144.67]:52933 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753285AbdBGLSq (ORCPT ); Tue, 7 Feb 2017 06:18:46 -0500 Date: Tue, 7 Feb 2017 22:18:40 +1100 From: Stephen Rothwell To: Greg KH Cc: Ulrich Hecht , linux-next@vger.kernel.org, "linux-kernel@vger.kernel.org" , Geert Uytterhoeven Subject: Re: linux-next: build warning after merge of the tty tree Message-ID: <20170207221840.29af3b84@canb.auug.org.au> In-Reply-To: <20170207083731.GA20338@kroah.com> References: <20170206151638.6e0f8a60@canb.auug.org.au> <20170206085042.GA3726@kroah.com> <20170207093709.0287cb68@canb.auug.org.au> <20170207083731.GA20338@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Greg, On Tue, 7 Feb 2017 09:37:31 +0100 Greg KH wrote: > > On Tue, Feb 07, 2017 at 09:37:09AM +1100, Stephen Rothwell wrote: > > > > I don't see that commit in any tree I have fetched. > > That is correct, it's in my "testing" branch that I use to stage things > in before it gets sent to the branch that you pull from. What an amusing idea ;-) > That branch is now merged with my -next branch, so you will see this > change the next time you sync. Thanks. -- Cheers, Stephen Rothwell