-next trees and my time this cycle

-next trees and my time this cycle

[Dave Airlie]

Hey all,

Hopefully all my sub-maintainers are awake and reading this.

So since Xmas is coming up and I've got an impending new arrival, I'm
betting this merge window might get a bit haphazard. So I'd like
people to start telling me now via git pull's what they'd like to get
in.

I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
people would like these in now, also anything I've missed on the list.
Other ARM maintainers (especially exynos) please try and get pull
requests in early. I might drop things that come in too late.

I expect the x86 folks and others who are pretty regular to not be a
problem (i.e. don't be a problem). Especially nouveau early is good
for me if you have anything.

Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Inki Dae]

Hi Dave,

2015년 12월 11일 15:58에 Dave Airlie 이(가) 쓴 글:
> Hey all,
> 
> Hopefully all my sub-maintainers are awake and reading this.
> 
> So since Xmas is coming up and I've got an impending new arrival, I'm
> betting this merge window might get a bit haphazard. So I'd like
> people to start telling me now via git pull's what they'd like to get
> in.
> 
> I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
> people would like these in now, also anything I've missed on the list.
> Other ARM maintainers (especially exynos) please try and get pull
> requests in early. I might drop things that come in too late.

Sorry for late. I am strugging for review and verification of exynos-drm-next tree.
This time, exynos drm tree will include below features,
- support runtime pm
- support dp panel dt binding using of graph concept.
- cleanup part of IPP enhancement patch series.

Now while I'm reviewing the cleanup part of IPP enhancement patch series, I found out a critical issue so as soon as I and original author resolve it, I will requst GIT PULL at least within next Monday.

Thanks,
Inki Dae

> 
> I expect the x86 folks and others who are pretty regular to not be a
> problem (i.e. don't be a problem). Especially nouveau early is good
> for me if you have anything.
> 
> Dave.
> 
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Russell King - ARM Linux]

On Fri, Dec 11, 2015 at 04:58:08PM +1000, Dave Airlie wrote:
> I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
> people would like these in now, also anything I've missed on the list.

I would definitely like to see etnaviv make it in for the next merge
window, but that depends on it being reviewed, and I haven't seen
anything from DRM people yet.

I've queued up some of the TDA998x and Armada DRM changes (3 and 5
patches respectively) which I'll send you shortly if they haven't
already been merged via some other route.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Liviu Dudau]

On Fri, Dec 11, 2015 at 04:58:08PM +1000, Dave Airlie wrote:
> Hey all,

Hi Dave,

> 
> Hopefully all my sub-maintainers are awake and reading this.
> 
> So since Xmas is coming up and I've got an impending new arrival, I'm
> betting this merge window might get a bit haphazard. So I'd like
> people to start telling me now via git pull's what they'd like to get
> in.
> 
> I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
> people would like these in now, also anything I've missed on the list.
> Other ARM maintainers (especially exynos) please try and get pull
> requests in early. I might drop things that come in too late.

I would like to include the HDLCD series as well if possible. I have
pushed it at git://linux-arm.org/linux-ld for-upstream/hdlcd but I can
send a pull request if you are happy to include it.

Best regards,
Liviu

> 
> I expect the x86 folks and others who are pretty regular to not be a
> problem (i.e. don't be a problem). Especially nouveau early is good
> for me if you have anything.
> 
> Dave.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Daniel Vetter]

On Fri, Dec 11, 2015 at 10:02:45AM +0000, Russell King - ARM Linux wrote:
> On Fri, Dec 11, 2015 at 04:58:08PM +1000, Dave Airlie wrote:
> > I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
> > people would like these in now, also anything I've missed on the list.
> 
> I would definitely like to see etnaviv make it in for the next merge
> window, but that depends on it being reviewed, and I haven't seen
> anything from DRM people yet.
> 
> I've queued up some of the TDA998x and Armada DRM changes (3 and 5
> patches respectively) which I'll send you shortly if they haven't
> already been merged via some other route.

I did look at etnaviv on v1, if all the things I've raised there have been
addressed (and it looks like, but no time for detailed checking):

Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

For detailed review it would be best to just get some of the new big
submissions to cross review I think. But personally I'd be ok with etnaviv
going in as is, trusting that you've done plenty of review within your
group.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Russell King - ARM Linux]

On Fri, Dec 11, 2015 at 05:15:40PM +0100, Daniel Vetter wrote:
> On Fri, Dec 11, 2015 at 10:02:45AM +0000, Russell King - ARM Linux wrote:
> > On Fri, Dec 11, 2015 at 04:58:08PM +1000, Dave Airlie wrote:
> > > I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
> > > people would like these in now, also anything I've missed on the list.
> > 
> > I would definitely like to see etnaviv make it in for the next merge
> > window, but that depends on it being reviewed, and I haven't seen
> > anything from DRM people yet.
> > 
> > I've queued up some of the TDA998x and Armada DRM changes (3 and 5
> > patches respectively) which I'll send you shortly if they haven't
> > already been merged via some other route.
> 
> I did look at etnaviv on v1, if all the things I've raised there have been
> addressed (and it looks like, but no time for detailed checking):

I did keep a list of your points, and made sure that we'd addressed
them all.  We went a little further towards the end with your 'flags'
suggestion for several of the ioctls, which I think was a very good
point you raised.

> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Thanks!

> For detailed review it would be best to just get some of the new big
> submissions to cross review I think. But personally I'd be ok with
> etnaviv going in as is, trusting that you've done plenty of review
> within your group.

We have had a certain amount of review within our group - Christian
reviewed many of my early patches, and I've reviewed Lucas' patches.
There could have been more review.

I was rather hoping for some review of the changes since your last
comments, especially with the locking changes.  I'm fairly confident
with the locking changes (which were particularly hairy) as I've been
running them for some time now with lockdep enabled.  The particularly
"hairy" bit was in etnaviv_gem_get_iova().

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Lucas Stach]

Am Freitag, den 11.12.2015, 17:36 +0000 schrieb Russell King - ARM
Linux:
> On Fri, Dec 11, 2015 at 05:15:40PM +0100, Daniel Vetter wrote:
> > On Fri, Dec 11, 2015 at 10:02:45AM +0000, Russell King - ARM Linux
> > wrote:
> > > On Fri, Dec 11, 2015 at 04:58:08PM +1000, Dave Airlie wrote:
> > > > I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans
> > > > for if
> > > > people would like these in now, also anything I've missed on
> > > > the list.
> > > 
> > > I would definitely like to see etnaviv make it in for the next
> > > merge
> > > window, but that depends on it being reviewed, and I haven't seen
> > > anything from DRM people yet.
> > > 
> > > I've queued up some of the TDA998x and Armada DRM changes (3 and
> > > 5
> > > patches respectively) which I'll send you shortly if they haven't
> > > already been merged via some other route.
> > 
> > I did look at etnaviv on v1, if all the things I've raised there
> > have been
> > addressed (and it looks like, but no time for detailed checking):
> 
> I did keep a list of your points, and made sure that we'd addressed
> them all.  We went a little further towards the end with your 'flags'
> suggestion for several of the ioctls, which I think was a very good
> point you raised.
> 
> > Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> Thanks!
> 
> > For detailed review it would be best to just get some of the new
> > big
> > submissions to cross review I think. But personally I'd be ok with
> > etnaviv going in as is, trusting that you've done plenty of review
> > within your group.
> 
> We have had a certain amount of review within our group - Christian
> reviewed many of my early patches, and I've reviewed Lucas' patches.
> There could have been more review.
> 
> I was rather hoping for some review of the changes since your last
> comments, especially with the locking changes.  I'm fairly confident
> with the locking changes (which were particularly hairy) as I've been
> running them for some time now with lockdep enabled.  The
> particularly
> "hairy" bit was in etnaviv_gem_get_iova().
> 
While I didn't review all of your patches in-depth, I think we've got
the locking changes pretty well covered. The review I did there wasn't
just some "I think this looks okay", but me taking the time to go
through all paths I could envision and validating that your locking
scheme works for them.

Regards,
Lucas 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Linus Torvalds]

On Thu, Dec 10, 2015 at 10:58 PM, Dave Airlie <airlied@gmail.com> wrote:
>
> So since Xmas is coming up and I've got an impending new arrival, I'm
> betting this merge window might get a bit haphazard. So I'd like
> people to start telling me now via git pull's what they'd like to get
> in.

So the rest of the world may not have an impending new arrival, but
with pretty much everybody doing Christmas break, I don't really
foresee opening the merge window immediately after the holidays. I
can't reasonably expect people to get ready for the merge window while
being drunk on eggnog or whatever.

If 4.4 stays on the usual schedule (and there's currently no big
reason to think it shouldn't), I'd do the final rc late December, and
final release on the Sunday of Jan 3rd.

But really, if I want people to be *ready* when the merge window
opens, rather than start working on it, I'd better delay the opening
of the merge window by at least a week.

So right now my tentative plan is to open the 4.5 merge window on Jan 10th.

Can't help with your impending new arrival, though. I thought you said
you had figured out why that kept happening?

                     Linus
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: -next trees and my time this cycle

[Dave Airlie]

On 13 December 2015 at 05:09, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Dec 10, 2015 at 10:58 PM, Dave Airlie <airlied@gmail.com> wrote:
>>
>> So since Xmas is coming up and I've got an impending new arrival, I'm
>> betting this merge window might get a bit haphazard. So I'd like
>> people to start telling me now via git pull's what they'd like to get
>> in.
>
> So the rest of the world may not have an impending new arrival, but
> with pretty much everybody doing Christmas break, I don't really
> foresee opening the merge window immediately after the holidays. I
> can't reasonably expect people to get ready for the merge window while
> being drunk on eggnog or whatever.
>
> If 4.4 stays on the usual schedule (and there's currently no big
> reason to think it shouldn't), I'd do the final rc late December, and
> final release on the Sunday of Jan 3rd.
>
> But really, if I want people to be *ready* when the merge window
> opens, rather than start working on it, I'd better delay the opening
> of the merge window by at least a week.
>
> So right now my tentative plan is to open the 4.5 merge window on Jan 10th.

Cool I might be a bit late, but that should work for me.

>
> Can't help with your impending new arrival, though. I thought you said
> you had figured out why that kept happening?

I thought becoming a kernel hacker would fix it.

Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel