All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Stephen Rothwell" <sfr@rothwell.id.au>,
	linux-next <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"David S . Miller" <davem@davemloft.net>,
	sparclinux@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: linux-next: lots of errors/warnings from the -Werror=missing-prototypes addition
Date: Thu, 30 Nov 2023 08:19:29 -0800	[thread overview]
Message-ID: <20231130081929.46a79c33edee8651c63112dc@linux-foundation.org> (raw)
In-Reply-To: <4be73872-c1f5-4c31-8201-712c19290a22@app.fastmail.com>

On Thu, 30 Nov 2023 09:07:38 +0100 "Arnd Bergmann" <arnd@arndb.de> wrote:

> > I guess it should precede "Makefile.extrawarn: turn on
> > missing-prototypes globally".
> 
> I already have a collection of patches to fix up known
> -Wmissing-prototype warnings across architectures in the
> asm-generic tree, so I'll add this patch there:
> 
> commit bdef96eb0b89dfa80992312a8e3b2613bf178ae5
> Author: Arnd Bergmann <arnd@arndb.de>
> Date:   Thu Nov 30 00:07:07 2023 +0100
> 
>     arch: turn off -Werror for architectures with known warnings

I think this would be better in the mm-nonmm tree, alongside
"Makefile.extrawarn: turn on missing-prototypes globally".  Can I steal it?

  reply	other threads:[~2023-11-30 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 20:58 linux-next: lots of errors/warnings from the -Werror=missing-prototypes addition Stephen Rothwell
2023-11-29 21:10 ` Andrew Morton
2023-11-29 22:51   ` Arnd Bergmann
2023-11-29 23:10     ` Andrew Morton
2023-11-30  8:07       ` Arnd Bergmann
2023-11-30 16:19         ` Andrew Morton [this message]
2023-11-30 21:36           ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231130081929.46a79c33edee8651c63112dc@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@rothwell.id.au \
    --cc=sparclinux@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.