linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:hch.procfs 7/42] include/linux/proc_fs.h:69:58: error: "0" may not appear in macro parameter list
Date: Thu, 17 May 2018 12:24:49 +0800	[thread overview]
Message-ID: <201805171246.OtRqzOhs%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4188 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git hch.procfs
head:   2f4293973d4eb8b6eb2f21f3db24461ac2b9e928
commit: 44414d82cfe0f68cb59d0a42f599ccd893ae0032 [7/42] proc: introduce proc_create_seq_private
config: h8300-h8300h-sim_defconfig (attached as .config)
compiler: h8300-linux-gcc (GCC) 7.2.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 44414d82cfe0f68cb59d0a42f599ccd893ae0032
        # save the attached .config to linux build tree
        make.cross ARCH=h8300 

Note: the vfs/hch.procfs HEAD 2f4293973d4eb8b6eb2f21f3db24461ac2b9e928 builds fine.
      It only hurts bisectibility.

All error/warnings (new ones prefixed by >>):

   In file included from kernel/fork.c:64:0:
>> include/linux/proc_fs.h:69:58: error: "0" may not appear in macro parameter list
    #define proc_create_seq_private(name, mode, parent, ops, 0, data) ({NULL;})
                                                             ^
--
   In file included from kernel/time/timer_list.c:13:0:
>> include/linux/proc_fs.h:69:58: error: "0" may not appear in macro parameter list
    #define proc_create_seq_private(name, mode, parent, ops, 0, data) ({NULL;})
                                                             ^
   kernel/time/timer_list.c: In function 'init_timer_list_procfs':
>> kernel/time/timer_list.c:379:7: error: implicit declaration of function 'proc_create_seq_private'; did you mean 'proc_create_seq_data'? [-Werror=implicit-function-declaration]
     pe = proc_create_seq_private("timer_list", 0400, NULL, &timer_list_sops,
          ^~~~~~~~~~~~~~~~~~~~~~~
          proc_create_seq_data
>> kernel/time/timer_list.c:379:5: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
     pe = proc_create_seq_private("timer_list", 0400, NULL, &timer_list_sops,
        ^
   cc1: some warnings being treated as errors
--
   In file included from kernel//time/timer_list.c:13:0:
>> include/linux/proc_fs.h:69:58: error: "0" may not appear in macro parameter list
    #define proc_create_seq_private(name, mode, parent, ops, 0, data) ({NULL;})
                                                             ^
   kernel//time/timer_list.c: In function 'init_timer_list_procfs':
   kernel//time/timer_list.c:379:7: error: implicit declaration of function 'proc_create_seq_private'; did you mean 'proc_create_seq_data'? [-Werror=implicit-function-declaration]
     pe = proc_create_seq_private("timer_list", 0400, NULL, &timer_list_sops,
          ^~~~~~~~~~~~~~~~~~~~~~~
          proc_create_seq_data
   kernel//time/timer_list.c:379:5: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
     pe = proc_create_seq_private("timer_list", 0400, NULL, &timer_list_sops,
        ^
   cc1: some warnings being treated as errors

vim +/0 +69 include/linux/proc_fs.h

    59	
    60	static inline struct proc_dir_entry *proc_symlink(const char *name,
    61			struct proc_dir_entry *parent,const char *dest) { return NULL;}
    62	static inline struct proc_dir_entry *proc_mkdir(const char *name,
    63		struct proc_dir_entry *parent) {return NULL;}
    64	static inline struct proc_dir_entry *proc_create_mount_point(const char *name) { return NULL; }
    65	static inline struct proc_dir_entry *proc_mkdir_data(const char *name,
    66		umode_t mode, struct proc_dir_entry *parent, void *data) { return NULL; }
    67	static inline struct proc_dir_entry *proc_mkdir_mode(const char *name,
    68		umode_t mode, struct proc_dir_entry *parent) { return NULL; }
  > 69	#define proc_create_seq_private(name, mode, parent, ops, 0, data) ({NULL;})
    70	#define proc_create_seq_data(name, mode, parent, ops, data) ({NULL;})
    71	#define proc_create_seq(name, mode, parent, ops) ({NULL;})
    72	#define proc_create(name, mode, parent, proc_fops) ({NULL;})
    73	#define proc_create_data(name, mode, parent, proc_fops, data) ({NULL;})
    74	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 4254 bytes --]

                 reply	other threads:[~2018-05-17  4:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201805171246.OtRqzOhs%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=hch@lst.de \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).