From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrey Albershteyn <aalbersh@kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] libxfs: fix compilation errors
Date: Wed, 14 Oct 2026 22:56:52 -0700 [thread overview]
Message-ID: <atBrJO9owC7yXsRb@infradead.org> (raw)
In-Reply-To: <20261014184212.GE1615495@frogsfrogsfrogs>
On Wed, Oct 14, 2026 at 11:42:12AM -0700, Darrick J. Wong wrote:
> Add -Werror=missing-prototype (or -Werror) to WARNINGS in
> include/builddefs.in:
>
> WARNINGS += -Werror
>
> Then rerun configure and make
Ah. This is not "compiler apply the default function declaration",
but the compiler warning about not having a prototype for a non-static
definition. Which is still somewhat useful, so I think we should
enable it as a warning (but not as an error like above) for xfsprogs
as well to stay in sync.
next prev parent reply other threads:[~2026-10-15 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:44 [PATCH] libxfs: fix compilation errors Darrick J. Wong
2026-10-14 18:24 ` Christoph Hellwig
2026-10-14 18:42 ` Darrick J. Wong
2026-10-15 5:56 ` Christoph Hellwig [this message]
2026-10-15 5:57 ` Christoph Hellwig
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=atBrJO9owC7yXsRb@infradead.org \
--to=hch@infradead.org \
--cc=aalbersh@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox