From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Chinner <david@fromorbit.com>,
Carlos Maiolino <cem@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
<linux-xfs@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the xfs tree
Date: Wed, 11 Dec 2024 09:04:45 +1100 [thread overview]
Message-ID: <20241211090445.3ca8dfed@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Hi all,
After merging the xfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/xfs/xfs_trans.c: In function '__xfs_trans_commit':
fs/xfs/xfs_trans.c:869:40: error: macro "xfs_trans_apply_dquot_deltas" requires 2 arguments, but only 1 given
869 | xfs_trans_apply_dquot_deltas(tp);
| ^
In file included from fs/xfs/xfs_trans.c:15:
fs/xfs/xfs_quota.h:176:9: note: macro "xfs_trans_apply_dquot_deltas" defined here
176 | #define xfs_trans_apply_dquot_deltas(tp, a)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
03d23e3ebeb7 ("xfs: don't lose solo dquot update transactions")
$ grep CONFIG_XFS_QUOTA .config
# CONFIG_XFS_QUOTA is not set
I have used the xfs tree from next-20241210 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-12-10 22:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 22:04 Stephen Rothwell [this message]
2024-12-11 9:44 ` linux-next: build failure after merge of the xfs tree Carlos Maiolino
2024-12-11 21:41 ` Carlos Maiolino
[not found] <jZld0KWAlgFM0KGNf6_lm-4ZXRf4uFdfuPXGopJi8jUD3StPMObAqCIaJUvNZvyoyxrWEJus6A_a0yxRt7X0Eg==@protonmail.internalid>
2025-07-18 0:08 ` Stephen Rothwell
2025-07-18 8:30 ` Carlos Maiolino
2025-07-18 8:33 ` Christoph Hellwig
2025-07-18 8:45 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 0:27 Stephen Rothwell
2019-10-28 23:11 Stephen Rothwell
2019-10-28 23:18 ` Darrick J. Wong
2019-10-29 5:56 ` Christoph Hellwig
2019-10-29 6:23 ` Stephen Rothwell
2019-10-29 6:32 ` Christoph Hellwig
2019-07-01 1:12 Stephen Rothwell
2016-02-09 0:17 Stephen Rothwell
2016-02-09 0:30 ` Eric Sandeen
2016-02-09 0:41 ` Stephen Rothwell
2015-04-20 2:35 Stephen Rothwell
2013-04-29 1:29 Stephen Rothwell
2013-04-29 1:40 ` Dave Chinner
2013-04-30 18:36 ` Ben Myers
2012-05-10 3:01 Stephen Rothwell
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:36 ` Mark Tinguely
2012-05-10 18:43 ` Ben Myers
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=20241211090445.3ca8dfed@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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