public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <yujie.liu@intel.com>
To: <liuchang_125125@163.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, <mark.tao@bayhubtech.com>,
	<shaper.liu@bayhubtech.com>, <thomas.hu@bayhubtech.com>,
	<chevron.li@bayhubtech.com>, <charl.liu@bayhubtech.com>,
	Charl Liu <liuchang_125125@163.com>
Subject: Re: [PATCH 3/9] scsi: bht: card: Add the source files related to card initialization
Date: Mon, 23 Oct 2023 09:00:30 +0800	[thread overview]
Message-ID: <202310220339.xnImSaRm-lkp@intel.com> (raw)
In-Reply-To: <20231013083320.10279-1-liuchang_125125@163.com>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 401644852d0b2a278811de38081be23f74b5bb04]

url:    https://github.com/intel-lab-lkp/linux/commits/liuchang_125125-163-com/scsi-Update-Kconfig-and-Makefile-for-supporting-Bayhub-s-SD-MMC-Card-interface-driver/20231017-123349
base:   401644852d0b2a278811de38081be23f74b5bb04
patch link:    https://lore.kernel.org/r/20231013083320.10279-1-liuchang_125125%40163.com
patch subject: [PATCH 3/9] scsi: bht: card: Add the source files related to card initialization
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202310220339.xnImSaRm-lkp@intel.com/

includecheck warnings: (new ones prefixed by >>)
>> drivers/scsi/bht/card/cardinterface.c: ../include/card.h is included more than once.
>> drivers/scsi/bht/card/cardinterface.c: ../include/cmdhandler.h is included more than once.
--
>> drivers/scsi/bht/card/output_tuning.c: ../include/card.h is included more than once.

vim +23 drivers/scsi/bht/card/cardinterface.c

  > 23	#include "../include/card.h"
    24	#include "../include/cardapi.h"
    25	#include "../include/hostapi.h"
    26	#include "../include/transhapi.h"
    27	#include "../include/hostvenapi.h"
    28	#include "../include/util.h"
    29	#include "../include/debug.h"
  > 30	#include "../include/cmdhandler.h"
    31	#include "../host/hostven.h"
  > 32	#include "../include/card.h"
    33	#include "../host/hostreg.h"
    34	#include "../include/funcapi.h"
    35	#include "../tagqueue/tq_trans_api.h"
  > 36	#include "../include/cmdhandler.h"
    37	#include "cardcommon.h"
    38	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


      parent reply	other threads:[~2023-10-23  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  8:33 [PATCH 3/9] scsi: bht: card: Add the source files related to card initialization liuchang_125125
2023-10-18  7:07 ` kernel test robot
2023-10-23  1:00 ` 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=202310220339.xnImSaRm-lkp@intel.com \
    --to=yujie.liu@intel.com \
    --cc=charl.liu@bayhubtech.com \
    --cc=chevron.li@bayhubtech.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=liuchang_125125@163.com \
    --cc=mark.tao@bayhubtech.com \
    --cc=martin.petersen@oracle.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shaper.liu@bayhubtech.com \
    --cc=thomas.hu@bayhubtech.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