From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] libxfs: fix build warnings
Date: Mon, 1 Dec 2025 23:37:33 -0800 [thread overview]
Message-ID: <aS6XPWlc3vBM0hPr@infradead.org> (raw)
In-Reply-To: <176463876118.839737.7691382070128152874.stgit@frogsfrogsfrogs>
On Mon, Dec 01, 2025 at 05:27:29PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> gcc 14.2 with all the warnings turn on complains about missing
> prototypes for these two functions:
I would have expected a lot more warnings from that in xfsprogs..
But the change itself looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-12-02 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 1:27 [PATCHSET 1/2] xfsprogs: various bug fixes for 6.18 Darrick J. Wong
2025-12-02 1:27 ` [PATCH 1/3] libxfs: fix build warnings Darrick J. Wong
2025-12-02 7:37 ` Christoph Hellwig [this message]
2025-12-02 1:27 ` [PATCH 2/3] xfs_db: document the rtsb command Darrick J. Wong
2025-12-02 7:37 ` Christoph Hellwig
2025-12-02 1:28 ` [PATCH 3/3] man2: fix getparents ioctl manpage Darrick J. Wong
2025-12-02 7:37 ` 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=aS6XPWlc3vBM0hPr@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 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.