On Thu, Dec 07, 2017 at 08:37:27PM +1100, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Wed, 6 Dec 2017 10:52:05 +0100 Daniel Vetter wrote:
> >
> > next-20171205 didn't have any of the patches in drm-intel/for-linux-next
> > that weren't already in the drm-next branch. My for-linux-next was at
> >
Hi Daniel,
On Wed, 6 Dec 2017 10:52:05 +0100 Daniel Vetter wrote:
>
> next-20171205 didn't have any of the patches in drm-intel/for-linux-next
> that weren't already in the drm-next branch. My for-linux-next was at
>
> commit 39ccc9852e2b46964c9c44eba52db57413ba6d27 (HEAD ->
> drm-intel-next-qu
On Wed, Dec 06, 2017 at 01:11:05PM +1100, Stephen Rothwell wrote:
> Hi Rodrigo,
>
> On Tue, 5 Dec 2017 17:19:21 -0800 Rodrigo Vivi wrote:
> >
> > We noticed that drm-intel/for-linux-next is currently disabled
> > on linux-next.
>
> What gave you that idea?
next-20171205 didn't have any of the p
On Dec 5, 2017, at 6:11 PM, Stephen Rothwell
mailto:s...@canb.auug.org.au>> wrote:
Hi Rodrigo,
On Tue, 5 Dec 2017 17:19:21 -0800 Rodrigo Vivi
mailto:rodrigo.v...@intel.com>> wrote:
We noticed that drm-intel/for-linux-next is currently disabled
on linux-next.
What gave you that idea?
Daniel
Hi Rodrigo,
On Tue, 5 Dec 2017 17:19:21 -0800 Rodrigo Vivi wrote:
>
> We noticed that drm-intel/for-linux-next is currently disabled
> on linux-next.
What gave you that idea?
> I wonder if it has to do with the compilation error we had yesterday
> night (enum plane related). Was it the case?
>
Hi Stephen,
We noticed that drm-intel/for-linux-next is currently disabled
on linux-next.
I wonder if it has to do with the compilation error we had yesterday
night (enum plane related). Was it the case?
Our solution on drm-tip was to fix at drm-rerere side when building
the branches so we don't
