public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm•com>
To: Daniel Vetter <daniel@ffwll•ch>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	dri-devel@lists•freedesktop.org
Subject: Re: Mali DP tree for linux-next
Date: Wed, 15 Jun 2016 17:15:15 +0100	[thread overview]
Message-ID: <20160615161515.GE9711@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <20160615152102.GH1338@phenom.ffwll.local>

On Wed, Jun 15, 2016 at 05:21:02PM +0200, Daniel Vetter wrote:
> On Wed, Jun 15, 2016 at 04:03:04PM +0100, Liviu Dudau wrote:
> > Hi Stephen,
> > 
> > I would like to add the Mali DP DRM driver tree to linux-next. I'm planning
> > to send a pull request for inclusion into v4.8 and I hope that getting a
> > wider exposure for a few weeks is beneficial.
> > 
> > Please add the following git tree:
> > 
> >    git://linux-arm.org/linux-ld for-upstream/mali-dp
> > 
> > It is based on drm-intel/topic/drm-misc tree, with the topic/drm-misc-2016-06-14 tag.
> 
> tbh just send Dave a pull request. It looks pretty nice, and inclusion in
> drm-next is even better than linux-next for handling any kinds of
> conflicts. And most of the driver trees aren't really active for more than
> 1 merge window it seems.

I can do that, of course. Wasn't sure if Dave is willing to pull stuff that hasn't
been fire proofed in linux-next.

As for driver trees, my HDLCD one sees regular activity ;)

Stephen,

I will send a pull request to David Airlie as well, but we plan to use this tree in the
future for more developments of the driver so I would appreciate if you add it to your
roaster of trees.

Best regards,
Liviu


> -Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists•freedesktop.org
> https://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
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-06-15 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 14:30 HDLCD tree for linux-next Liviu Dudau
2015-12-30 22:00 ` Stephen Rothwell
2016-06-15 15:03 ` Mali DP " Liviu Dudau
2016-06-15 15:21   ` Daniel Vetter
2016-06-15 16:15     ` Liviu Dudau [this message]
2016-06-15 23:37   ` Stephen Rothwell

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=20160615161515.GE9711@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm$(echo .)com \
    --cc=daniel@ffwll$(echo .)ch \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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