linux-kernel - Re: linux-next: Tree for May 2

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: <20190503080331.0ccc2419@canb.auug.org.au>
Date:   Fri, 3 May 2019 08:03:31 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     Nathan Chancellor <natechancellor@...il.com>,
        Anders Roxell <anders.roxell@...aro.org>,
        maxime.ripard@...tlin.com, andre.przywara@....com,
        samuel@...lland.org,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for May 2

Hi Daniel,

On Thu, 2 May 2019 22:09:49 +0200 Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>
> Yes, I picked the patch and it was merged it via the tip tree [1] as
> requested by Marc Zyngier [2] and notified [3].
> 
> In any case, this patch should have go through my tree initially, so if
> it is found somewhere else that's wrong.
> 
> I did a respin of my branch and pushed it again in case there was
> something wrong from it.

The patch ("clocksource/drivers/arch_timer: Workaround for Allwinner
A64 timer instability") was merged into v5.1-rc1 via the tip tree as
you say, however the version of your clockevents tree in yesterday's
linux-next was based on v5.0-rc1 and contained the patch again ...

Today's should be better.
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped