devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: hehuan1@eswincomputing.com, ulf.hansson@linaro.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	jszhang@kernel.org, adrian.hunter@intel.com,
	p.zabel@pengutronix.de, linux-mmc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, ningyu@eswincomputing.com,
	linmin@eswincomputing.com, pinkesh.vaghela@einfochips.com,
	xuxiang@eswincomputing.com, luyulin@eswincomputing.com,
	dongxuyang@eswincomputing.com, zhangsenchuan@eswincomputing.com,
	weishangjuan@eswincomputing.com, lizhi2@eswincomputing.com,
	caohang@eswincomputing.com, hehuan1@eswincomputing.com
Subject: Re: [PATCH v3 2/2] mmc: sdhci-of-dwcmshc: Add support for Eswin EIC7700
Date: Sat, 11 Oct 2025 09:54:24 +0800	[thread overview]
Message-ID: <202510110904.0H6EStUB-lkp@intel.com> (raw)
In-Reply-To: <20251010094109.1613-1-hehuan1@eswincomputing.com>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on ulf-hansson-mmc-mirror/next v6.17 next-20251010]
[cannot apply to robh/for-next pza/reset/next pza/imx-drm/next]
[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/hehuan1-eswincomputing-com/dt-bindings-mmc-sdhci-of-dwcmshc-Add-Eswin-EIC7700/20251010-174323
base:   linus/master
patch link:    https://lore.kernel.org/r/20251010094109.1613-1-hehuan1%40eswincomputing.com
patch subject: [PATCH v3 2/2] mmc: sdhci-of-dwcmshc: Add support for Eswin EIC7700
config: x86_64-randconfig-005-20251011 (https://download.01.org/0day-ci/archive/20251011/202510110904.0H6EStUB-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251011/202510110904.0H6EStUB-lkp@intel.com/reproduce)

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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202510110904.0H6EStUB-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/mmc/host/sdhci-of-dwcmshc.c:300:13: error: redefinition of 'dwcmshc_enable_card_clk'
     300 | static void dwcmshc_enable_card_clk(struct sdhci_host *host)
         |             ^~~~~~~~~~~~~~~~~~~~~~~
   drivers/mmc/host/sdhci-of-dwcmshc.c:289:13: note: previous definition of 'dwcmshc_enable_card_clk' with type 'void(struct sdhci_host *)'
     289 | static void dwcmshc_enable_card_clk(struct sdhci_host *host)
         |             ^~~~~~~~~~~~~~~~~~~~~~~
   drivers/mmc/host/sdhci-of-dwcmshc.c: In function 'sdhci_eic7700_set_clock':
   drivers/mmc/host/sdhci-of-dwcmshc.c:1179:9: error: implicit declaration of function 'dwcmshc_disable_card_clk'; did you mean 'dwcmshc_enable_card_clk'? [-Wimplicit-function-declaration]
    1179 |         dwcmshc_disable_card_clk(host);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~
         |         dwcmshc_enable_card_clk
   drivers/mmc/host/sdhci-of-dwcmshc.c: At top level:
>> drivers/mmc/host/sdhci-of-dwcmshc.c:289:13: warning: 'dwcmshc_enable_card_clk' defined but not used [-Wunused-function]
     289 | static void dwcmshc_enable_card_clk(struct sdhci_host *host)
         |             ^~~~~~~~~~~~~~~~~~~~~~~


vim +/dwcmshc_enable_card_clk +289 drivers/mmc/host/sdhci-of-dwcmshc.c

   288	
 > 289	static void dwcmshc_enable_card_clk(struct sdhci_host *host)
   290	{
   291		u16 ctrl;
   292	
   293		ctrl = sdhci_readw(host, SDHCI_CLOCK_CONTROL);
   294		if ((ctrl & SDHCI_CLOCK_INT_EN) && !(ctrl & SDHCI_CLOCK_CARD_EN)) {
   295			ctrl |= SDHCI_CLOCK_CARD_EN;
   296			sdhci_writew(host, ctrl, SDHCI_CLOCK_CONTROL);
   297		}
   298	}
   299	

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

      parent reply	other threads:[~2025-10-11  1:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10  9:38 [PATCH v3 0/2] Add support for Eswin EIC7700 SD/eMMC controller hehuan1
2025-10-10  9:40 ` [PATCH v3 1/2] dt-bindings: mmc: sdhci-of-dwcmshc: Add Eswin EIC7700 hehuan1
2025-10-10 14:33   ` Conor Dooley
2025-10-10  9:41 ` [PATCH v3 2/2] mmc: sdhci-of-dwcmshc: Add support for " hehuan1
2025-10-11  0:39   ` kernel test robot
2025-10-11  1:54   ` 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=202510110904.0H6EStUB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=caohang@eswincomputing.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dongxuyang@eswincomputing.com \
    --cc=hehuan1@eswincomputing.com \
    --cc=jszhang@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linmin@eswincomputing.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lizhi2@eswincomputing.com \
    --cc=luyulin@eswincomputing.com \
    --cc=ningyu@eswincomputing.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=p.zabel@pengutronix.de \
    --cc=pinkesh.vaghela@einfochips.com \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=weishangjuan@eswincomputing.com \
    --cc=xuxiang@eswincomputing.com \
    --cc=zhangsenchuan@eswincomputing.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;
as well as URLs for NNTP newsgroup(s).