linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Laurence Oberman <loberman@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	loberman@redhat.com, rdunlap@infradead.org, tglx@linutronix.de
Subject: Re: [PATCH] V4 init/main.c Enable watchdog_thresh control from kernel line
Date: Tue, 30 Oct 2018 10:01:22 +0800	[thread overview]
Message-ID: <201810301002.F2ZG8t7E%fengguang.wu@intel.com> (raw)
In-Reply-To: <1540404366-26999-1-git-send-email-loberman@redhat.com>

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

Hi Laurence,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linux-sof-driver/master]
[also build test ERROR on v4.19 next-20181029]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Laurence-Oberman/V4-init-main-c-Enable-watchdog_thresh-control-from-kernel-line/20181025-040136
base:   https://github.com/thesofproject/linux master
config: i386-randconfig-k3-10291547 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   init/main.c: In function 'is_watchdog_thresh_setup':
>> init/main.c:1036:20: error: 'watchdog_thresh' undeclared (first use in this function); did you mean 'proc_watchdog_thresh'?
     get_option(&str, &watchdog_thresh);
                       ^~~~~~~~~~~~~~~
                       proc_watchdog_thresh
   init/main.c:1036:20: note: each undeclared identifier is reported only once for each function it appears in

vim +1036 init/main.c

  1033	
  1034	static int __init is_watchdog_thresh_setup(char *str)
  1035	{
> 1036		get_option(&str, &watchdog_thresh);
  1037		return 1;
  1038	}
  1039	__setup("watchdog_thresh=", is_watchdog_thresh_setup);
  1040	
  1041	

---
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: 27373 bytes --]

      parent reply	other threads:[~2018-10-30  2:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 18:06 [PATCH] V4 init/main.c Enable watchdog_thresh control from kernel line Laurence Oberman
2018-10-24 18:14 ` Randy Dunlap
2018-10-24 19:04 ` Randy Dunlap
2018-10-30  2:01 ` kbuild 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=201810301002.F2ZG8t7E%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    /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).