linux-kernel - Re: at91 git 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-prev] [day] [month] [year] [list]

Message-ID: <20201123225906.7cd6d14e@canb.auug.org.au>
Date:   Mon, 23 Nov 2020 22:59:06 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Ludovic Desroches <ludovic.desroches@...rochip.com>,
        ksummit <ksummit-discuss@...ts.linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: at91 git tree in linux-next

Hi Geert,

On Mon, 23 Nov 2020 11:44:17 +0100 Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> How is this working?
> 
> From next-20201123:
> 
>     Merging at91/at91-next (0698efbb33ef Merge branches 'at91-soc',
> 'at91-dt' and 'at91-defconfig' into at91-next)
> 
> which is indeed a recent commit, while Next/Trees has the wrong repo
> (linux-at91.git instead of linux.git):

That is what happens when you store the (supposedly) same information
in 2 places :-(  I have fixed the incorrect one.

Thanks for letting me know.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped