linux-kernel - Re: [GIT PULL 3/4] ARM: exynos: soc/mach for v4.20, second round

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: <CAK8P3a2+wyge4=eCxJps0Ar3bYFrqjvdMakiYHBPmn3p63+GDg@mail.gmail.com>
Date:   Thu, 11 Oct 2018 16:02:45 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Krzysztof Kozlowski <krzk@...nel.org>
Cc:     Olof Johansson <olof@...om.net>, arm@...nel.org,
        Kukjin Kim <kgene@...nel.org>,
        linux-arm-kernel@...ts.infradead.org,
        linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL 3/4] ARM: exynos: soc/mach for v4.20, second round

On 10/10/18, Krzysztof Kozlowski <krzk@...nel.org> wrote:
> Hi,
>
> On top of previous pull request.
>
> ----------------------------------------------------------------
> Samsung mach/soc changes for v4.20, second round
>
> 1. Disable SAMSUNG_PM_CHECK Kconfig feature incompatible with Exynos.
>

I suspect Olof made a small mistake when he pulled the previous branch
into next/dt instead of next/soc, so I ended up pulling the new branch
with all commits into next/soc again.

Nothing harmful happened and you did everything right, I was just
a bit confused by this.

Thanks,

       Arnd