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 v2 3/4] memory: tegra: Add support for multiple irqs
Date: Fri, 3 Oct 2025 14:28:36 +0800 [thread overview]
Message-ID: <202510031456.NUbQMKPs-lkp@intel.com> (raw)
In-Reply-To: <20251002090054.1837481-4-ketanp@nvidia.com>
Hi Ketan,
kernel test robot noticed the following build errors:
[auto build test ERROR on tegra/for-next]
[also build test ERROR on linus/master v6.17 next-20251002]
[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/20251002-171042
base: https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
patch link: https://lore.kernel.org/r/20251002090054.1837481-4-ketanp%40nvidia.com
patch subject: [PATCH v2 3/4] memory: tegra: Add support for multiple irqs
config: arm64-randconfig-003-20251003 (https://download.01.org/0day-ci/archive/20251003/202510031456.NUbQMKPs-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251003/202510031456.NUbQMKPs-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/202510031456.NUbQMKPs-lkp@intel.com/
All errors (new ones prefixed by >>):
aarch64-linux-ld: Unexpected GOT/PLT entries detected!
aarch64-linux-ld: Unexpected run-time procedure linkages detected!
aarch64-linux-ld: arch/arm64/kernel/signal.o: in function `restore_sigframe':
signal.c:(.text+0x1a28): undefined reference to `restore_gcs_context'
aarch64-linux-ld: arch/arm64/kernel/signal.o: in function `setup_sigframe':
signal.c:(.text+0x2574): undefined reference to `preserve_gcs_context'
>> aarch64-linux-ld: drivers/memory/tegra/tegra186.o:(.rodata+0xc8): undefined reference to `tegra30_mc_irq_handlers'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-03 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:00 [PATCH v2 0/4] memory: tegra: Add MC error logging support for Tegra264 SoC Ketan Patil
2025-10-02 9:00 ` [PATCH v2 1/4] memory: tegra: Group mc-err related registers Ketan Patil
2025-10-02 9:00 ` [PATCH v2 2/4] memory: tegra: Group register and fields Ketan Patil
2025-10-02 9:00 ` [PATCH v2 3/4] memory: tegra: Add support for multiple irqs Ketan Patil
2025-10-03 6:28 ` kernel test robot [this message]
2025-10-02 9:00 ` [PATCH v2 4/4] memory: tegra: Add MC error logging support for Tegra264 Ketan Patil
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=202510031456.NUbQMKPs-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