From: Dave Chinner <david@fromorbit.com>
To: kbuild test robot <lkp@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
kbuild-all@01.org, linux-xfs@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [xfs-linux:iomap-for-next 3/12] include/trace/events/iomap.h:49:39: warning: 'struct page' declared inside parameter list will not be visible outside of this definition or declaration
Date: Mon, 9 Sep 2019 07:38:53 +1000 [thread overview]
Message-ID: <20190908213853.GC16973@dread.disaster.area> (raw)
In-Reply-To: <201909072347.PRqg4Chr%lkp@intel.com>
On Sat, Sep 07, 2019 at 11:52:49PM +0800, kbuild test robot wrote:
> tree: https://kernel.googlesource.com/pub/scm/fs/xfs/xfs-linux.git iomap-for-next
> head: 68494b8e248fe8a7b6e9f88edd9a87661760ddb9
> commit: 4b45a4b5c1f5f52728cec1ce60a3a8f5bb9521b4 [3/12] iomap: add tracing for the address space operations
> config: nds32-allyesconfig (attached as .config)
> compiler: nds32le-linux-gcc (GCC) 8.1.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 4b45a4b5c1f5f52728cec1ce60a3a8f5bb9521b4
> # save the attached .config to linux build tree
> GCC_VERSION=8.1.0 make.cross ARCH=nds32
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/trace/events/iomap.h:15,
> from <command-line>:
> >> include/trace/events/iomap.h:49:39: warning: 'struct page' declared inside parameter list will not be visible outside of this definition or declaration
> TP_PROTO(struct inode *inode, struct page *page, unsigned long off, \
The only file that includes trace/events/iomap.h most definitely
has already defined struct page, and
> include/trace/events/iomap.h:49:18: warning: 'struct inode' declared inside parameter list will not be visible outside of this definition or declaration
> TP_PROTO(struct inode *inode, struct page *page, unsigned long off, \
> ^~~~~
struct inode as well.
So I'm not sure where the error is actually coming from, nor why it
might only be generated by an obscure architecture (I've never heard
of nds32 until now).
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-09-08 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 15:52 [xfs-linux:iomap-for-next 3/12] include/trace/events/iomap.h:49:39: warning: 'struct page' declared inside parameter list will not be visible outside of this definition or declaration kbuild test robot
2019-09-08 21:38 ` Dave Chinner [this message]
2019-09-10 6:47 ` 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=20190908213853.GC16973@dread.disaster.area \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
/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).