Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753150Ab3GAIwv (ORCPT ); Mon, 1 Jul 2013 04:52:51 -0400 Received: from mail-oa0-f41.google.com ([209.85.219.41]:54749 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752974Ab3GAIwt (ORCPT ); Mon, 1 Jul 2013 04:52:49 -0400 MIME-Version: 1.0 X-Originating-IP: [178.83.130.250] In-Reply-To: References: Date: Mon, 1 Jul 2013 10:52:49 +0200 Message-ID: Subject: Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ] From: Daniel Vetter To: Sedat Dilek , "Barnes, Jesse" Cc: Stephen Rothwell , linux-next , Linux Kernel Mailing List , intel-gfx , DRI , Dave Airlie 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: 1206 Lines: 36 On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote: > On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20130628: >> >> The regulator tree gained a build failure so I used the version from >> next-20130628. >> >> The trivial tree gained a conflict against the fbdev tree. >> >> The arm-soc tree gained a conflict against the net-next tree. >> >> The akpm tree lost a few patches that turned up elsewhere and I removed 2 >> that were causing run time problems. >> > > [ CC drm and drm-intel folks ] > > [ Did not check any relevant MLs ] > > Please, see attached dmesg output. Clock mismatch, one for Jesse to figure out. Note that this patch is for 3.12, I simply haven't yet gotten around to properly split my patch queue so a few spilled into -next. I'll do that now. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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/