The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ketan Patil <ketanp@nvidia.com>,
	krzk@kernel.org, thierry.reding@gmail.com, jonathanh@nvidia.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org, Ketan Patil <ketanp@nvidia.com>
Subject: Re: [PATCH 3/4] memory: tegra: Add support for multiple irqs
Date: Mon, 22 Sep 2025 09:39:22 +0800	[thread overview]
Message-ID: <202509220945.sf6Ru7V3-lkp@intel.com> (raw)
In-Reply-To: <20250916051754.39250-4-ketanp@nvidia.com>

Hi Ketan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tegra/for-next]
[also build test WARNING on krzk-mem-ctrl/for-next linus/master v6.17-rc7 next-20250919]
[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/Ketan-Patil/memory-tegra-Group-mc-err-related-registers/20250916-132118
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
patch link:    https://lore.kernel.org/r/20250916051754.39250-4-ketanp%40nvidia.com
patch subject: [PATCH 3/4] memory: tegra: Add support for multiple irqs
config: arm-randconfig-r121-20250922 (https://download.01.org/0day-ci/archive/20250922/202509220945.sf6Ru7V3-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project efd96afedf2c0f6f2cc34cf5a9a7e3e78f592255)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250922/202509220945.sf6Ru7V3-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/202509220945.sf6Ru7V3-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/memory/tegra/tegra20.c:764:21: sparse: sparse: symbol 'tegra20_mc_irq_handlers' was not declared. Should it be static?

vim +/tegra20_mc_irq_handlers +764 drivers/memory/tegra/tegra20.c

   763	
 > 764	const irq_handler_t tegra20_mc_irq_handlers[] = {
   765		tegra20_mc_handle_irq
   766	};
   767	

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

  reply	other threads:[~2025-09-22  1:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  5:17 [PATCH 0/4] memory: tegra: Add MC error logging support for Tegra264 SoC Ketan Patil
2025-09-16  5:17 ` [PATCH 1/4] memory: tegra: Group mc-err related registers Ketan Patil
2025-09-16  5:17 ` [PATCH 2/4] memory: tegra: Group register and fields Ketan Patil
2025-09-16  5:17 ` [PATCH 3/4] memory: tegra: Add support for multiple irqs Ketan Patil
2025-09-22  1:39   ` kernel test robot [this message]
2025-09-16  5:17 ` [PATCH 4/4] memory: tegra: Add MC error logging support for Tegra264 Ketan Patil
2025-09-17  1:32   ` kernel test robot
2025-09-17  2:09   ` Krzysztof Kozlowski

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=202509220945.sf6Ru7V3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jonathanh@nvidia.com \
    --cc=ketanp@nvidia.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=thierry.reding@gmail.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