From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Liviu Dudau <Liviu.Dudau@arm•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
dri-devel@lists•freedesktop.org
Subject: Re: Mali DP tree for linux-next
Date: Thu, 16 Jun 2016 09:37:00 +1000 [thread overview]
Message-ID: <20160616093700.26f5b117@canb.auug.org.au> (raw)
In-Reply-To: <20160615150304.GD9711@e106497-lin.cambridge.arm.com>
Hi Liviu,
On Wed, 15 Jun 2016 16:03:04 +0100 Liviu Dudau <Liviu.Dudau@arm•com> wrote:
>
> 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.
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
_______________________________________________
dri-devel mailing list
dri-devel@lists•freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-06-15 23:37 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
2016-06-15 23:37 ` Stephen Rothwell [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=20160616093700.26f5b117@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Liviu.Dudau@arm$(echo .)com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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