[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170195271166.2310221.13174919656650959020.b4-ty@ellerman.id.au>
Date: Thu, 07 Dec 2023 23:38:31 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Mahesh J Salgaonkar <mahesh@...ux.ibm.com>,
Palmer Dabbelt <palmer@...osinc.com>,
Arnd Bergmann <arnd@...db.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Nathan Lynch <nathanl@...ux.ibm.com>
Cc: lkft-triage@...ts.linaro.org, Benjamin Gray <bgray@...ux.ibm.com>,
Arnd Bergmann <arnd@...db.de>,
Nathan Chancellor <nathan@...nel.org>,
Anders Roxell <anders.roxell@...aro.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
clang-built-linux <llvm@...ts.linux.dev>,
regressions@...ts.linux.dev,
Linux Kernel Functional Testing <lkft@...aro.org>
Subject: Re: [PATCH] powerpc/rtas_pci: rename and properly expose config access APIs
On Mon, 27 Nov 2023 18:40:09 -0600, Nathan Lynch wrote:
> The rtas_read_config() and rtas_write_config() functions in
> kernel/rtas_pci.c have external linkage and two users in arch/powerpc:
> the rtas_pci code itself and the pseries platform's "enhanced error
> handling" (EEH) support code.
>
> The prototypes for these functions in asm/ppc-pci.h have until now
> been guarded by CONFIG_EEH since the only external caller is the
> pseries EEH code. However, this presumably has always generated
> warnings when built with !CONFIG_EEH and -Wmissing-prototypes:
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/rtas_pci: rename and properly expose config access APIs
https://git.kernel.org/powerpc/c/9be4feb768b86c25da336a6c0f3e3caefd16f1e4
cheers
Powered by blists - more mailing lists