[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbL1mfcAz9sPn89UGSQ6tb=jF6nRYAwp9Qz8zLXLLU_UA@mail.gmail.com>
Date: Tue, 7 Nov 2023 09:06:41 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] powerpc: Fix signature of pfn_to_kaddr()
On Tue, Nov 7, 2023 at 6:57 AM Michael Ellerman <mpe@...erman.id.au> wrote:
> I'm struggling to connect the removal of const with those bug reports.
> It looks like all those warnings are about 0xc000000000000000 being
> outside the range of unsigned long when building 32-bit.
Aha right. I wonder what actually causes that.
> Is it the right bug report link?
Yeah I'm just bad at understanding these reports.
> The current signature of:
>
> static inline const void *pfn_to_kaddr(unsigned long pfn) ...
>
> seems OK to me.
OK then, drop this patch.
Yours,
Linus Walleij
Powered by blists - more mailing lists