mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zhen Ni <nizhen@uniontech.com>,
	mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, mcgrof@kernel.org,
	keescook@chromium.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, Zhen Ni <nizhen@uniontech.com>
Subject: Re: [PATCH] sched: move deadline_period sysctls to deadline.c
Date: Sun, 13 Feb 2022 20:12:15 +0800	[thread overview]
Message-ID: <202202132047.Oh4JMFtB-lkp@intel.com> (raw)
In-Reply-To: <20220211070014.30764-1-nizhen@uniontech.com>

Hi Zhen,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on tip/sched/core]
[also build test ERROR on linus/master kees/for-next/pstore v5.17-rc3 next-20220211]
[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/0day-ci/linux/commits/Zhen-Ni/sched-move-deadline_period-sysctls-to-deadline-c/20220211-150312
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git c8eaf6ac76f40f6c59fc7d056e2e08c4a57ea9c7
config: arm-randconfig-c002-20220213 (https://download.01.org/0day-ci/archive/20220213/202202132047.Oh4JMFtB-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/c785b6fd90f2f1a7dc49c7fcbd30ad54ecff0e75
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Zhen-Ni/sched-move-deadline_period-sysctls-to-deadline-c/20220211-150312
        git checkout c785b6fd90f2f1a7dc49c7fcbd30ad54ecff0e75
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash

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

All errors (new ones prefixed by >>):

>> kernel/sched/deadline.c:49:20: error: 'sched_dl_sysctl_init' defined but not used [-Werror=unused-function]
      49 | static void __init sched_dl_sysctl_init(void)
         |                    ^~~~~~~~~~~~~~~~~~~~
   cc1: all warnings being treated as errors


vim +/sched_dl_sysctl_init +49 kernel/sched/deadline.c

    48	
  > 49	static void __init sched_dl_sysctl_init(void)
    50	{
    51		register_sysctl_init("kernel", sched_dl_sysctls);
    52	}
    53	#else
    54	#define sched_dl_sysctl_init() do { } while (0)
    55	#endif
    56	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

      reply	other threads:[~2022-02-13 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  7:00 Zhen Ni
2022-02-13 12:12 ` kernel test robot [this message]

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=202202132047.Oh4JMFtB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=juri.lelli@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nizhen@uniontech.com \
    --cc=vincent.guittot@linaro.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

all inboxes | Powered by JetHome®