From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755675AbcEYCDV (ORCPT ); Tue, 24 May 2016 22:03:21 -0400 Received: from ozlabs.org ([103.22.144.67]:60941 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754133AbcEYCDU (ORCPT ); Tue, 24 May 2016 22:03:20 -0400 Date: Wed, 25 May 2016 12:03:18 +1000 From: Stephen Rothwell To: Linus Torvalds Cc: Dave Airlie , DRI mailing list , Linux Kernel Mailing List Subject: Re: [git pull] drm for v4.7 Message-ID: <20160525120318.407c3aa0@canb.auug.org.au> In-Reply-To: References: 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 Linus, On Mon, 23 May 2016 12:10:25 -0700 Linus Torvalds wrote: > > Is there a patch pending for this that I'm not aware of, or is it just > that nobody but me hates spurious warnings? Didn't this show up in > linux-next? And if it _did_ show up in linux-next, why was the pull > request not talking about it? My bad. That warning turned up in linux-next last Wednesday but I didn't notice (I have other stuff to do and don't carefully watch all the builds all day - and there are quite a few warnings to filter new ones out out of). Maybe I need some automated way to flag new warnings. -- Cheers, Stephen Rothwell