[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a78d9dcd-0bc1-7e98-a8f1-e5d6cd0c09a3@intel.com>
Date: Thu, 18 May 2023 14:56:52 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Arnd Bergmann <arnd@...nel.org>, x86@...nel.org
Cc: Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Juergen Gross <jgross@...e.com>,
"Srivatsa S. Bhat (VMware)" <srivatsa@...il.mit.edu>,
Alexey Makhalov <amakhalov@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
Peter Zijlstra <peterz@...radead.org>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...radead.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
linux-pci@...r.kernel.org, platform-driver-x86@...r.kernel.org,
xen-devel@...ts.xenproject.org, linux-pm@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH 00/20] x86: address -Wmissing-prototype warnings
On 5/16/23 12:35, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> This addresses all x86 specific prototype warnings. The majority of the
> patches should be straightforward, either adding an #include statement
> to get the right header, or ensuring that an unused global function is
> left out of the build when the prototype is hidden.
>
> The ones that are a bit awkward are those that just add a prototype to
> shut up the warning, but the prototypes are never used for calling the
> function because the only caller is in assembler code. I tried to come up
> with other ways to shut up the compiler using the asmlinkage annotation,
> but with no success.
>
> All of the warnings have to be addressed in some form before the warning
> can be enabled by default.
I picked up the ones that were blatantly obvious, but left out 03, 04,
10, 12 and 19 for the moment.
BTW, I think the i386 allyesconfig is getting pretty lightly tested
these days. I think you and I hit the same mlx4 __bad_copy_from()
compile issue.
Powered by blists - more mailing lists