linux-kernel - Updating sunxi tree in linux-next

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-next>] [day] [month] [year] [list]

Message-ID: <20170331075729.gsfewphm3zd45vwt@lukather>
Date:   Fri, 31 Mar 2017 09:57:29 +0200
From:   Maxime Ripard <maxime.ripard@...e-electrons.com>
To:     sfr@...b.auug.org.au
Cc:     Chen-Yu Tsai <wens@...e.org>, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Updating sunxi tree in linux-next

Hi Stephen,

We've switched from my personal git tree for the Allwinner sunxi
development to a shared tree:
git://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git

The branch to be included in linux-next will still be called
sunxi/for-next as it used to be, and it will still go through the
arm-soc tree to reach Linux.

However, I'll still have the patches for our DRM drivers on my
personal git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git

Could you add the branch sunxi-drm/for-next to the list of branches
you merge?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)