Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753483Ab3F2Xel (ORCPT ); Sat, 29 Jun 2013 19:34:41 -0400 Received: from mail-la0-f49.google.com ([209.85.215.49]:58300 "EHLO mail-la0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750976Ab3F2Xej (ORCPT ); Sat, 29 Jun 2013 19:34:39 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 30 Jun 2013 09:34:37 +1000 Message-ID: Subject: Re: Linux 3.10-rc7 From: Dave Airlie To: Linus Torvalds Cc: Sergey Meirovich , David Airlie , Alex Deucher , Jerome Glisse , Linux Kernel Mailing List , DRI Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1136 Lines: 29 On Sun, Jun 30, 2013 at 8:13 AM, Linus Torvalds wrote: > On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich wrote: >>> (and possibly the >>> mkregtable binary) and trying again might fix it. >> >> Removing mkregtable has indeed the compile issue for me. Thanks! > > Ok, so something failed at an earlier build. That error is probably > long gone, though, since the subsequent build failure ends up being > just a symptom rather than the underlying cause. > >>> Which still leaves >>> us with the question of how this happened, and a potentially fragile >>> Makefile. > > Radeon/drm people - any ideas how that mkregtable failure happened? > I'd care if we can definitely rule out previous power fails or forced reboots. Otherwise just seems like noise, if gcc can produce 0 sized binaries then I'm sure we'd have other issues. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/