[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170502184132.2c1b0299@canb.auug.org.au>
Date: Tue, 2 May 2017 18:41:32 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Daniel Vetter <daniel@...ll.ch>
Cc: Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
ARM <linux-arm-kernel@...ts.infradead.org>,
Dave Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Intel Graphics <intel-gfx@...ts.freedesktop.org>,
DRI <dri-devel@...ts.freedesktop.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Logan Gunthorpe <logang@...tatee.com>,
Sumit Semwal <sumit.semwal@...aro.org>,
Jens Wiklander <jens.wiklander@...aro.org>
Subject: Re: linux-next: build failure after merge of the drm-misc tree
Hi Daniel,
On Tue, 2 May 2017 10:25:18 +0200 Daniel Vetter <daniel@...ll.ch> wrote:
>
> Since this is an all-new driver it might be best to stagger the pull
> requests and merge the new tee subsystem (or whatever it is) after drm?
>
> Not sure what to best do here ...
This will merge via Dave, so Dave just needs to let Linus know that a
fix up is needed when this merges with the arm-soc stuff in Linus' tree.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists