From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757958AbcIPIfB (ORCPT ); Fri, 16 Sep 2016 04:35:01 -0400 Received: from mail-wm0-f49.google.com ([74.125.82.49]:36781 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756556AbcIPIet (ORCPT ); Fri, 16 Sep 2016 04:34:49 -0400 Date: Fri, 16 Sep 2016 09:34:44 +0100 From: Peter Griffin To: Stephen Rothwell Cc: Vinod Koul , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the slave-dma tree Message-ID: <20160916083444.GA4730@griffinp-ThinkPad-X1-Carbon-2nd> References: <20160916131834.1ecb0eeb@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160916131834.1ecb0eeb@canb.auug.org.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vinod & Stephen, On Fri, 16 Sep 2016, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig build) failed like this: FYI Patch 17 of 19 in the fdma series "drm/virtio: kconfig: Fix recursive dependency issue." [1], fixes this issue. It looks like that hasn't been applied. I should have made it clearer that this was a depedency (and the other white drm/kconfig white space fixup obviously isn't). https://lkml.org/lkml/2016/9/5/328 regards, Peter.