From: Daniel Vetter <daniel@ffwll•ch>
To: Joerg Roedel <jroedel@suse•de>
Cc: Tomasz Figa <tfiga@chromium•org>,
linaro-kernel@lists•linaro.org, Simon Xue <xxm@rock-chips•com>,
kernel-build-reports@lists•linaro.org,
dri-devel <dri-devel@lists•freedesktop.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists•infradead.org>,
Mark Brown <broonie@kernel•org>,
linux-next@vger•kernel.org,
Shunqian Zheng <zhengsq@rock-chips•com>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>
Subject: Re: next-20160707 build: 1 failures 6 warnings (next-20160707)
Date: Tue, 12 Jul 2016 15:59:04 +0200 [thread overview]
Message-ID: <20160712135904.GJ23520@phenom.ffwll.local> (raw)
In-Reply-To: <20160707153237.GF11467@suse.de>
On Thu, Jul 07, 2016 at 05:32:37PM +0200, Joerg Roedel wrote:
> On Thu, Jul 07, 2016 at 10:18:02PM +0900, Tomasz Figa wrote:
> > This is probably because we missed this hidden dependency and decided
> > to push the IOMMU part separately through the IOMMU tree. I guess we
> > can remove the offending patch from the IOMMU tree and let the DRM
> > tree include it based on a topic branch from Joerg.
> >
> > Joerg, David, Mark Yao, what do you think?
>
> Will the DRM patches go upstream soon, or is there still discussion
> around them? For now I am going to remove/revert that patch in my tree.
drm is pretty much done for 4.8, but as usual there's some driver
maintainers who are rather late. I'd say unlikely it lands in 4.8,
postpone to 4.9 seems more reasonable given the trouble it just caused.
-Daniel
>
>
> Joerg
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists•freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2016-07-12 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 9:23 next-20160707 build: 1 failures 6 warnings (next-20160707) Build bot for Mark Brown
2016-07-07 12:22 ` Mark Brown
2016-07-07 13:18 ` Tomasz Figa
[not found] ` <CAAFQd5DacKar+T1Fj62NvAZOT_QWBhahftZJXGq40Z19n-Z4Hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-07 15:32 ` Joerg Roedel
2016-07-12 13:59 ` Daniel Vetter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160712135904.GJ23520@phenom.ffwll.local \
--to=daniel@ffwll$(echo .)ch \
--cc=broonie@kernel$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=jroedel@suse$(echo .)de \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=tfiga@chromium$(echo .)org \
--cc=xxm@rock-chips$(echo .)com \
--cc=zhengsq@rock-chips$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox