mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: jingyuwang <jingyuwang_vip@163.com>,
	akpm@linux-foundation.org, rostedt@goodmis.org,
	mhiramat@kernel.org, vbabka@suse.cz, ahalaney@redhat.com,
	Jason@zx2c4.com, mark-pk.tsai@mediatek.com
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	jingyuwang <jingyuwang_vip@163.com>
Subject: Re: [PATCH] Fix the following checkpatch error:
Date: Tue, 14 Jun 2022 09:26:50 +0800	[thread overview]
Message-ID: <202206140910.24mkxBXB-lkp@intel.com> (raw)
In-Reply-To: <20220613202210.31759-1-jingyuwang_vip@163.com>

Hi jingyuwang,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on linus/master v5.19-rc2 next-20220610]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/intel-lab-lkp/linux/commits/jingyuwang/Fix-the-following-checkpatch-error/20220614-050258
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20220614/202206140910.24mkxBXB-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/intel-lab-lkp/linux/commit/35742a839670fa8937c7040160e16b7009b2a9ae
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review jingyuwang/Fix-the-following-checkpatch-error/20220614-050258
        git checkout 35742a839670fa8937c7040160e16b7009b2a9ae
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   init/main.c:773:20: warning: no previous prototype for 'arch_post_acpi_subsys_init' [-Wmissing-prototypes]
     773 | void __init __weak arch_post_acpi_subsys_init(void) { }
         |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~
   init/main.c:785:20: warning: no previous prototype for 'mem_encrypt_init' [-Wmissing-prototypes]
     785 | void __init __weak mem_encrypt_init(void) { }
         |                    ^~~~~~~~~~~~~~~~
   init/main.c:787:20: warning: no previous prototype for 'poking_init' [-Wmissing-prototypes]
     787 | void __init __weak poking_init(void) { }
         |                    ^~~~~~~~~~~
   In file included from include/linux/printk.h:6,
                    from include/linux/kernel.h:29,
                    from include/linux/cpumask.h:10,
                    from include/linux/mm_types_task.h:14,
                    from include/linux/mm_types.h:5,
                    from include/linux/buildid.h:5,
                    from include/linux/module.h:14,
                    from init/main.c:17:
>> include/linux/init.h:316:27: error: '__setup_str_initcall_blacklist' causes a section type conflict with 'initcall_level_names'
     316 |         static const char __setup_str_##unique_id[] __initconst         \
         |                           ^~~~~~~~~~~~
   include/linux/init.h:329:9: note: in expansion of macro '__setup_param'
     329 |         __setup_param(str, fn, fn, 0)
         |         ^~~~~~~~~~~~~
   init/main.c:1239:1: note: in expansion of macro '__setup'
    1239 | __setup("initcall_blacklist=", initcall_blacklist);
         | ^~~~~~~
   init/main.c:1344:20: note: 'initcall_level_names' was declared here
    1344 | static const char *initcall_level_names[] __initconst = {
         |                    ^~~~~~~~~~~~~~~~~~~~


vim +316 include/linux/init.h

^1da177e4c3f41 Linus Torvalds 2005-04-16  308  
^1da177e4c3f41 Linus Torvalds 2005-04-16  309  /*
^1da177e4c3f41 Linus Torvalds 2005-04-16  310   * Only for really core code.  See moduleparam.h for the normal way.
^1da177e4c3f41 Linus Torvalds 2005-04-16  311   *
^1da177e4c3f41 Linus Torvalds 2005-04-16  312   * Force the alignment so the compiler doesn't space elements of the
^1da177e4c3f41 Linus Torvalds 2005-04-16  313   * obs_kernel_param "array" too far apart in .init.setup.
^1da177e4c3f41 Linus Torvalds 2005-04-16  314   */
^1da177e4c3f41 Linus Torvalds 2005-04-16  315  #define __setup_param(str, unique_id, fn, early)			\
fd6c3a8dc44329 Jan Beulich    2009-03-12 @316  	static const char __setup_str_##unique_id[] __initconst		\
fd6c3a8dc44329 Jan Beulich    2009-03-12  317  		__aligned(1) = str; 					\
^1da177e4c3f41 Linus Torvalds 2005-04-16  318  	static struct obs_kernel_param __setup_##unique_id		\
33def8498fdde1 Joe Perches    2020-10-21  319  		__used __section(".init.setup")				\
147ad605dc12c5 Johan Hovold   2020-11-23  320  		__aligned(__alignof__(struct obs_kernel_param))		\
^1da177e4c3f41 Linus Torvalds 2005-04-16  321  		= { __setup_str_##unique_id, fn, early }
^1da177e4c3f41 Linus Torvalds 2005-04-16  322  

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  reply	other threads:[~2022-06-14  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 20:22 jingyuwang
2022-06-14  1:26 ` kernel test robot [this message]
2022-06-14  4:55 ` kernel test robot
2022-06-14  5:27 ` kernel test robot

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=202206140910.24mkxBXB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jason@zx2c4.com \
    --cc=ahalaney@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jingyuwang_vip@163.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark-pk.tsai@mediatek.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vbabka@suse.cz \
    /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

all inboxes | Powered by JetHome®