linux-kernel - Re: linux-next: build failure after merge of the v4l-dvb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170206091914.56836dd3@canb.auug.org.au>
Date:   Mon, 6 Feb 2017 09:19:14 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Mauro Carvalho Chehab <mchehab@....samsung.com>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Sean Young <sean@...s.org>
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree

Hi Mauro,

On Thu, 2 Feb 2017 22:24:35 -0200 Mauro Carvalho Chehab <mchehab@....samsung.com> wrote:
>
> So, if this is not a problem to you, maybe you can setup your
> environment to pull (in this order) from:
> 
> 	git://linuxtv.org/media_tree.git fixes
> 	git://linuxtv.org/media_tree.git master
> 	git://linuxtv.org/mchehab/media-next.git master
> 
> Most of the time, the last pull won't get anything.

OK, from today I have those three trees called v4l-dvb-fixes, v4l-dvb
and v4l-dvb-next respectively.  We'll see how it goes.

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@...b.auug.org.au