Re: [PATCH] powerpc: Fix signature of pfn_to_kaddr()

2023-11-09 Thread Michael Ellerman
Linus Walleij writes: > On Tue, Nov 7, 2023 at 6:57 AM Michael Ellerman wrote: > >> I'm struggling to connect the removal of const with those bug reports. >> It looks like all those warnings are about 0xc000 being >> outside the range of unsigned long when building 32-bit. > > Aha rig

Re: [PATCH] powerpc: Fix signature of pfn_to_kaddr()

2023-11-08 Thread Christophe Leroy
Le 07/11/2023 à 06:57, Michael Ellerman a écrit : > Linus Walleij writes: >> There is a const in the returned value from pfn_to_kaddr() >> but there are consumers that want to modify the result >> and the generic function pfn_to_virt() in >> does allow this, so let's relax this requirement and

Re: [PATCH] powerpc: Fix signature of pfn_to_kaddr()

2023-11-07 Thread Linus Walleij
On Tue, Nov 7, 2023 at 6:57 AM Michael Ellerman wrote: > I'm struggling to connect the removal of const with those bug reports. > It looks like all those warnings are about 0xc000 being > outside the range of unsigned long when building 32-bit. Aha right. I wonder what actually cause

Re: [PATCH] powerpc: Fix signature of pfn_to_kaddr()

2023-11-06 Thread Michael Ellerman
Linus Walleij writes: > There is a const in the returned value from pfn_to_kaddr() > but there are consumers that want to modify the result > and the generic function pfn_to_virt() in > does allow this, so let's relax this requirement and do not > make the returned value const. > > Reported-by: k

[PATCH] powerpc: Fix signature of pfn_to_kaddr()

2023-11-06 Thread Linus Walleij
There is a const in the returned value from pfn_to_kaddr() but there are consumers that want to modify the result and the generic function pfn_to_virt() in does allow this, so let's relax this requirement and do not make the returned value const. Reported-by: kernel test robot Closes: https://l