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@xxxxxxxxx> > > 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@xxxxxxxxxxxxx
