From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S970918AbdEZJVX (ORCPT ); Fri, 26 May 2017 05:21:23 -0400 Received: from mail-qk0-f173.google.com ([209.85.220.173]:32901 "EHLO mail-qk0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422825AbdEZJEs (ORCPT ); Fri, 26 May 2017 05:04:48 -0400 MIME-Version: 1.0 In-Reply-To: <20170526183541.2cf1f92c@canb.auug.org.au> References: <20170519132317.5dc47b24@canb.auug.org.au> <20170519220931.GA24990@fury> <20170526093412.3af222e6@canb.auug.org.au> <20170526183541.2cf1f92c@canb.auug.org.au> From: Andy Shevchenko Date: Fri, 26 May 2017 12:04:47 +0300 Message-ID: Subject: Re: linux-next: build warning after merge of the drivers-x86 tree To: Stephen Rothwell Cc: Arnd Bergmann , Darren Hart , Linux-Next Mailing List , Linux Kernel Mailing List , Ritesh Raj Sarraf , Andy Shevchenko Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 26, 2017 at 11:35 AM, Stephen Rothwell wrote: > On Fri, 26 May 2017 10:25:36 +0200 Arnd Bergmann wrote: >> >> Andy wrote that he committed an updated patch on May 23. The git tree >> at git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git#for-next >> appears to currently contain an older state from May 15. > > So just not pushed out yet. That's fine, I will hopefully notice when > it turns up. Just checking that it wasn't forgotten. No, it wasn't, it it in testing branch, I 'm about to push to for-next. -- With Best Regards, Andy Shevchenko