From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Whitehouse <swhiteho@redhat•com>,
Bob Peterson <rpeterso@redhat•com>
Cc: Andreas Gruenbacher <agruenba@redhat•com>,
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 gfs2 tree
Date: Wed, 20 Oct 2021 09:22:58 +1100 [thread overview]
Message-ID: <20211020092258.71861678@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi all,
After merging the gfs2 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from fs/gfs2/glock.c:39:
fs/gfs2/glock.c: In function 'may_grant':
fs/gfs2/glock.c:332:16: error: passing argument 2 of 'gfs2_dump_glock' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
332 | GLOCK_BUG_ON(gl, !test_bit(HIF_HOLDER,
| ^~
fs/gfs2/glock.h:222:26: note: in definition of macro 'GLOCK_BUG_ON'
222 | gfs2_dump_glock(NULL, gl, true); \
| ^~
fs/gfs2/glock.h:219:70: note: expected 'struct gfs2_glock *' but argument is of type 'const struct gfs2_glock *'
219 | extern void gfs2_dump_glock(struct seq_file *seq, struct gfs2_glock *gl,
| ~~~~~~~~~~~~~~~~~~~^~
cc1: all warnings being treated as errors
Caused by commit
9d0f1e82baf2 ("gfs2: Introduce flag for glock holder auto-demotion")
I have used the gfs2 tree from next-20211019 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-10-19 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 22:22 Stephen Rothwell [this message]
2021-10-19 23:21 ` linux-next: build failure after merge of the gfs2 tree Andreas Grünbacher
-- strict thread matches above, loose matches on Subject: below --
2021-06-09 3:07 Stephen Rothwell
2021-06-10 12:35 ` Andreas Gruenbacher
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=20211020092258.71861678@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=agruenba@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rpeterso@redhat$(echo .)com \
--cc=swhiteho@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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