linux-kernel - Re: [PATCH] SoC: polarfire: fix build warning

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: <3fedb4c6-baa5-2107-934d-31f8205176b4@microchip.com>
Date:   Mon, 28 Feb 2022 17:09:50 +0100
From:   Nicolas Ferre <nicolas.ferre@...rochip.com>
To:     Arnd Bergmann <arnd@...nel.org>, Conor Dooley <mail@...chuod.ie>
CC:     Lewis Hanly <lewis.hanly@...rochip.com>,
        Nathan Chancellor <nathan@...nel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Conor Dooley <conor.dooley@...rochip.com>,
        Arnd Bergmann <arnd@...db.de>,
        "kernel test robot" <lkp@...el.com>,
        Jassi Brar <jaswinder.singh@...aro.org>,
        linux-riscv <linux-riscv@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        <llvm@...ts.linux.dev>
Subject: Re: [PATCH] SoC: polarfire: fix build warning

On 28/02/2022 at 16:41, Arnd Bergmann wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Mon, Feb 28, 2022 at 4:35 PM Conor Dooley <mail@...chuod.ie> wrote:
>>
>> I had sent a fix for the build warning on saturday morning - but I guess
>> you missed it.
>>
>> Thanks for fixing it anyway :)
> 
> Thank you for your quick reply. I had indeed missed that fix. You did the
> right thing here by sending it to Nicolas, but he hasn't had a chance to forward
> it to soc@...nel.org yet, so it was not visible in patchwork.
> 
> As it turns out, your patch is correct and mine was wrong anyway, so I
> have now replaced my patch with yours.
> 
> Nicolas, I hope that doesn't cause you extra work. If you have picked it
> up into your tree, you can drop it again from there.

No problem on my side: I was planning to add it to another PR to you but 
it's far easier if you already took it directly.

Thanks Arnd, best regards,
   Nicolas


-- 
Nicolas Ferre