Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: John Garry <john.garry@huawei.com>,
	jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: kbuild-all@lists.01.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linuxarm@huawei.com,
	Luo Jiaxing <luojiaxing@huawei.com>,
	John Garry <john.garry@huawei.com>
Subject: Re: [PATCH 3/3] scsi: hisi_sas: Move debugfs code to v3 hw driver
Date: Tue, 24 Nov 2020 05:29:33 +0800	[thread overview]
Message-ID: <202011240532.tzUuowni-lkp@intel.com> (raw)
In-Reply-To: <1606153296-60088-4-git-send-email-john.garry@huawei.com>

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

Hi John,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on scsi/for-next linus/master v5.10-rc5 next-20201123]
[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/John-Garry/hisi_sas-A-small-bunch-of-misc-patches/20201124-014754
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/ede79ead19f599aecdc68447f3bfd6418df29561
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review John-Garry/hisi_sas-A-small-bunch-of-misc-patches/20201124-014754
        git checkout ede79ead19f599aecdc68447f3bfd6418df29561
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

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

All warnings (new ones prefixed by >>):

>> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:4371:6: warning: no previous prototype for 'debugfs_init_v3_hw' [-Wmissing-prototypes]
    4371 | void debugfs_init_v3_hw(struct hisi_hba *hisi_hba)
         |      ^~~~~~~~~~~~~~~~~~

vim +/debugfs_init_v3_hw +4371 drivers/scsi/hisi_sas/hisi_sas_v3_hw.c

  4370	
> 4371	void debugfs_init_v3_hw(struct hisi_hba *hisi_hba)
  4372	{
  4373		struct device *dev = hisi_hba->dev;
  4374		int i;
  4375	
  4376		hisi_hba->debugfs_dir = debugfs_create_dir(dev_name(dev),
  4377							   hisi_sas_debugfs_dir);
  4378		debugfs_create_file("trigger_dump", 0200,
  4379				    hisi_hba->debugfs_dir,
  4380				    hisi_hba,
  4381				    &debugfs_trigger_dump_v3_hw_fops);
  4382	
  4383		/* create bist structures */
  4384		debugfs_bist_init_v3_hw(hisi_hba);
  4385	
  4386		hisi_hba->debugfs_dump_dentry =
  4387				debugfs_create_dir("dump", hisi_hba->debugfs_dir);
  4388	
  4389		debugfs_phy_down_cnt_init_v3_hw(hisi_hba);
  4390	
  4391		for (i = 0; i < hisi_sas_debugfs_dump_count; i++) {
  4392			if (debugfs_alloc_v3_hw(hisi_hba, i)) {
  4393				debugfs_remove_recursive(hisi_hba->debugfs_dir);
  4394				dev_dbg(dev, "failed to init debugfs!\n");
  4395				break;
  4396			}
  4397		}
  4398	}
  4399	

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

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

      reply	other threads:[~2020-11-23 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 17:41 [PATCH 0/3] hisi_sas: A small bunch of misc patches John Garry
2020-11-23 17:41 ` [PATCH 1/3] scsi: hisi_sas: Reduce some indirection in v3 hw driver John Garry
2020-11-23 17:41 ` [PATCH 2/3] scsi: hisi_sas: Fix up probe error handling for v3 hw John Garry
2020-11-23 17:41 ` [PATCH 3/3] scsi: hisi_sas: Move debugfs code to v3 hw driver John Garry
2020-11-23 21:29   ` 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=202011240532.tzUuowni-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jejb@linux.ibm.com \
    --cc=john.garry@huawei.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=luojiaxing@huawei.com \
    --cc=martin.petersen@oracle.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