Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1297497 > unrolled thread

HDLCD tree for linux-next

Back to article view | Back to linux.kernel

Contents

  HDLCD tree for linux-next Liviu Dudau <Liviu.Dudau@arm.com> - 2015-12-23 15:40 +0100
    Re: HDLCD tree for linux-next Stephen Rothwell <sfr@canb.auug.org.au> - 2015-12-30 23:10 +0100

#1297497 — HDLCD tree for linux-next

Hi Stephen,

I would like to add the HDLCD DRM driver tree to linux-next. I'm planning
to send a pull request for inclusion into v4.5 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/hdlcd

It is based on Dave Airlie's drm-next tree as of 23rd of December.

Many thanks,
Liviu

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1299521

Hi Liviu,

On Wed, 23 Dec 2015 14:30:23 +0000 Liviu Dudau <Liviu.Dudau@arm.com> wrote:
>
> I would like to add the HDLCD DRM driver tree to linux-next. I'm planning
> to send a pull request for inclusion into v4.5 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/hdlcd
> 
> It is based on Dave Airlie's drm-next tree as of 23rd of December.

Added from today (though there may not be a release until Monday).

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web