Re: linux-next: build failure after merge of the slave-dma tree

From	Vinod Koul <vinod.koul@intel.com>
Newsgroups	linux.kernel
Subject	Re: linux-next: build failure after merge of the slave-dma tree
Date	2016-09-19 18:40 +0200
Message-ID	<sj9LQ-7Ol-3@gated-at.bofh.it> (permalink)
References	<shRR0-7qg-3@gated-at.bofh.it> <shWQH-2fE-45@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Sep 16, 2016 at 09:34:44AM +0100, Peter Griffin wrote:
> 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).

Yeah it should have been mentioned.

And I do not like to merge DRM patches for this and that too without ACKs.

I am dropping this branch from next untill I get ACK from someone on DRM
side to apply this

Thanks
-- 
~Vinod

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

linux-next: build failure after merge of the slave-dma tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-09-16 05:20 +0200
  Re: linux-next: build failure after merge of the slave-dma tree Peter Griffin <peter.griffin@linaro.org> - 2016-09-16 10:40 +0200
    Re: linux-next: build failure after merge of the slave-dma tree Vinod Koul <vinod.koul@intel.com> - 2016-09-19 18:40 +0200

csiph-web