On Fri, Apr 19, 2024, at 07:12, Michael Ellerman wrote:
> Michael Ellerman writes:
>> "Arnd Bergmann" writes:
>>>
>>> I had included this at first, but then I still ran into
>>> the same warnings because it ends up pulling in the
>>> generic outsb() etc from include/asm-generic/io.h
>>> that reli
Michael Ellerman writes:
> "Arnd Bergmann" writes:
>> On Thu, Apr 18, 2024, at 08:26, Michael Ellerman wrote:
>>> Arnd Bergmann writes:
>>
>>> @@ -692,6 +692,7 @@ static inline void name at
>>> \
>>> #define writesw writesw
>>> #define writesl writesl
>>>
>>>
"Arnd Bergmann" writes:
> On Thu, Apr 18, 2024, at 08:26, Michael Ellerman wrote:
>> Arnd Bergmann writes:
>
>> @@ -692,6 +692,7 @@ static inline void name at
>> \
>> #define writesw writesw
>> #define writesl writesl
>>
>> +#ifdef CONFIG_HAS_IOPORT
>> #define
On Thu, Apr 18, 2024, at 08:26, Michael Ellerman wrote:
> Arnd Bergmann writes:
> @@ -692,6 +692,7 @@ static inline void name at
> \
> #define writesw writesw
> #define writesl writesl
>
> +#ifdef CONFIG_HAS_IOPORT
> #define inb inb
> #define inw inw
> #defi
Michael Ellerman writes:
> Arnd Bergmann writes:
>> From: Arnd Bergmann
>>
>> Calling inb()/outb() on powerpc when CONFIG_PCI is disabled causes
>> a NULL pointer dereference, which is bad for a number of reasons.
>>
>> After my patch to turn on -Werror in linux-next, this caused a
>> compiler-t
Arnd Bergmann writes:
> From: Arnd Bergmann
>
> Calling inb()/outb() on powerpc when CONFIG_PCI is disabled causes
> a NULL pointer dereference, which is bad for a number of reasons.
>
> After my patch to turn on -Werror in linux-next, this caused a
> compiler-time warning with clang:
>
> In file
From: Arnd Bergmann
Calling inb()/outb() on powerpc when CONFIG_PCI is disabled causes
a NULL pointer dereference, which is bad for a number of reasons.
After my patch to turn on -Werror in linux-next, this caused a
compiler-time warning with clang:
In file included from arch/powerpc/include/as
