public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kah.jing.lee@intel.com, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, arnd@arndb.de
Cc: kbuild-all@lists.01.org, rafael.j.wysocki@intel.com,
	tien.sung.ang@intel.com, dinh.nguyen@intel.com,
	Kah Jing Lee <kah.jing.lee@intel.com>,
	Zhou@vger.kernel.org, Furong <furong.zhou@intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v2 1/3] drivers: misc: intel_sysid: Add sysid from arch to drivers
Date: Sun, 14 Aug 2022 20:07:28 +0800	[thread overview]
Message-ID: <202208141908.sFdK5QCc-lkp@intel.com> (raw)
In-Reply-To: <20220721123149.416618-1-kah.jing.lee@intel.com>

Hi,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on staging/staging-testing]
[also build test WARNING on soc/for-next v5.19]
[cannot apply to char-misc/char-misc-testing linus/master next-20220812]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/kah-jing-lee-intel-com/drivers-misc-intel_sysid-Add-sysid-from-arch-to-drivers/20220721-213214
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 8af028c2b22bc04f5ab59cd39fa97ccf14aa8f25
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20220814/202208141908.sFdK5QCc-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/intel-lab-lkp/linux/commit/5e0d691312542fbb751afb99bd7b537b9a975750
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review kah-jing-lee-intel-com/drivers-misc-intel_sysid-Add-sysid-from-arch-to-drivers/20220721-213214
        git checkout 5e0d691312542fbb751afb99bd7b537b9a975750
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/misc/

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

sparse warnings: (new ones prefixed by >>)
>> drivers/misc/intel_sysid.c:66:24: sparse: sparse: symbol 'intel_sysid_attr_group' was not declared. Should it be static?

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

  parent reply	other threads:[~2022-08-14 12:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 12:20 [PATCH 0/2] New driver for Intel(Altera) FPGA System ID softIP kah.jing.lee
2022-06-03  6:41 ` Greg KH
2022-06-03  7:35   ` kah.jing.lee
2022-07-21 12:30 ` [PATCH v2 0/3] " kah.jing.lee
2022-07-21 12:31   ` [PATCH v2 1/3] drivers: misc: intel_sysid: Add sysid from arch to drivers kah.jing.lee
2022-07-27 21:02     ` kernel test robot
2022-07-28  7:53     ` Greg KH
2022-07-28 15:37       ` Pierre-Louis Bossart
2022-07-28 15:59         ` Greg KH
2022-07-28 16:53           ` Pierre-Louis Bossart
2022-07-29 11:43             ` Greg KH
2022-07-29 11:56               ` Greg KH
2022-07-29 13:57                 ` Greg KH
2022-07-28  7:57     ` Greg KH
2022-08-14 12:07     ` kernel test robot [this message]
2022-07-21 12:32   ` [PATCH v2 2/3] dt-bindings: misc: intel_sysid: Add the system id binding for Altera(Intel) FPGA platform kah.jing.lee
2022-07-21 19:16     ` Greg KH
2022-07-25  3:47       ` kah.jing.lee
2022-07-25  3:56     ` [PATCH v3 " kah.jing.lee
2022-07-21 12:32   ` [PATCH v2 3/3] documentation: misc: intel_sysid: Add the system id sysfs documentation " kah.jing.lee
2022-07-21 19:16     ` Greg KH
2022-07-25  3:59     ` [PATCH v3 " kah.jing.lee
2022-07-28  7:51       ` Greg KH
2022-07-28  7:58   ` [PATCH v2 0/3] New driver for Intel(Altera) FPGA System ID softIP Greg KH

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=202208141908.sFdK5QCc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Zhou@vger.kernel.org \
    --cc=arnd@arndb.de \
    --cc=dinh.nguyen@intel.com \
    --cc=furong.zhou@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kah.jing.lee@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tien.sung.ang@intel.com \
    /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