From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Jiang <dave.jiang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <mawilcox@microsoft.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: linux-next: build warning from Linus' tree
Date: Mon, 27 Feb 2017 10:23:01 +1100 [thread overview]
Message-ID: <20170227102301.24133c04@canb.auug.org.au> (raw)
Hi all,
With just Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
produced this warning:
fs/dax.c: In function 'dax_iomap_fault':
fs/dax.c:1462:35: warning: passing argument 2 of 'dax_iomap_pmd_fault' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
return dax_iomap_pmd_fault(vmf, ops);
^
fs/dax.c:1439:12: note: expected 'struct iomap_ops *' but argument is of type 'const struct iomap_ops *'
static int dax_iomap_pmd_fault(struct vm_fault *vmf, struct iomap_ops *ops)
^
Introduced by commit
a2d581675d48 ("mm,fs,dax: change ->pmd_fault to ->huge_fault")
which missed fixing up the !CONFIG_FS_DAX_PMD case.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-02-26 23:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 23:23 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 7:20 linux-next: build warning from Linus' tree Stephen Rothwell
2021-07-08 2:25 ` Stephen Rothwell
2021-07-20 7:31 ` Stephen Rothwell
2021-08-10 9:29 ` Stephen Rothwell
2019-08-29 22:23 Stephen Rothwell
2019-08-29 22:29 ` Thomas Gleixner
2019-08-30 0:25 ` Stephen Rothwell
2011-06-03 1:10 Stephen Rothwell
2011-06-03 14:17 ` David Sterba
2011-06-03 1:00 Stephen Rothwell
2010-10-27 0:29 Stephen Rothwell
2010-10-27 0:58 ` Jesse Gross
2010-10-27 0:00 Stephen Rothwell
2010-09-24 4:08 Stephen Rothwell
2010-09-24 12:32 ` Frederic Weisbecker
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=20170227102301.24133c04@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).