public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jyan Chou <jyanchou@realtek.com>,
	adrian.hunter@intel.com, ulf.hansson@linaro.org,
	jh80.chung@samsung.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	benchuanggli@gmail.com, jyanchou@realtek.com
Subject: Re: [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver
Date: Thu, 19 Oct 2023 21:00:31 +0800	[thread overview]
Message-ID: <202310192006.ZUfTNe5e-lkp@intel.com> (raw)
In-Reply-To: <20231018055326.18256-2-jyanchou@realtek.com>

Hi Jyan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc6 next-20231019]
[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/Jyan-Chou/mmc-solve-DMA-boundary-limitation-of-CQHCI-driver/20231018-135532
base:   linus/master
patch link:    https://lore.kernel.org/r/20231018055326.18256-2-jyanchou%40realtek.com
patch subject: [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20231019/202310192006.ZUfTNe5e-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231019/202310192006.ZUfTNe5e-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/202310192006.ZUfTNe5e-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/mmc/host/cqhci-core.c:477:6: warning: no previous prototype for function 'cqhci_set_tran_desc' [-Wmissing-prototypes]
   void cqhci_set_tran_desc(u8 *desc, dma_addr_t addr, int len, bool end,
        ^
   drivers/mmc/host/cqhci-core.c:477:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   void cqhci_set_tran_desc(u8 *desc, dma_addr_t addr, int len, bool end,
   ^
   static 
   1 warning generated.


vim +/cqhci_set_tran_desc +477 drivers/mmc/host/cqhci-core.c

   476	
 > 477	void cqhci_set_tran_desc(u8 *desc, dma_addr_t addr, int len, bool end,
   478					bool dma64)
   479	{
   480		__le32 *attr = (__le32 __force *)desc;
   481	
   482		*attr = (CQHCI_VALID(1) |
   483			 CQHCI_END(end ? 1 : 0) |
   484			 CQHCI_INT(0) |
   485			 CQHCI_ACT(0x4) |
   486			 CQHCI_DAT_LENGTH(len));
   487	
   488		if (dma64) {
   489			__le64 *dataddr = (__le64 __force *)(desc + 4);
   490	
   491			dataddr[0] = cpu_to_le64(addr);
   492		} else {
   493			__le32 *dataddr = (__le32 __force *)(desc + 4);
   494	
   495			dataddr[0] = cpu_to_le32(addr);
   496		}
   497	}
   498	EXPORT_SYMBOL(cqhci_set_tran_desc);
   499	

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

  parent reply	other threads:[~2023-10-19 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  5:53 [PATCH V2][0/4] Add DesignWare Mobile mmc driver Jyan Chou
2023-10-18  5:53 ` [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver Jyan Chou
2023-10-19  9:00   ` kernel test robot
2023-10-19 13:00   ` kernel test robot [this message]
2023-10-18  5:53 ` [PATCH V2][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver Jyan Chou
2023-10-18  5:53 ` [PATCH V2][3/4] mmc: Add dw mobile mmc cmdq rtk driver Jyan Chou
2023-10-18  5:53 ` [PATCH V2][4/4] mmc: Add dt-bindings for realtek mmc driver Jyan Chou
2023-10-18 14:24   ` Krzysztof Kozlowski
2023-10-20  5:18     ` Jyan Chou [周芷安]
2023-10-21 11:46   ` kernel test robot

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=202310192006.ZUfTNe5e-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=benchuanggli@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=jyanchou@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ulf.hansson@linaro.org \
    /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