From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v1 1/2] spi: zynq-qspi: read flash above 16 MiB via the extended address register
Date: Fri, 13 Nov 2026 08:46:57 +0800 [thread overview]
Message-ID: <202611130828.KCC0t13G-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "linux-review patch is more than 7 days old, verify it wasn't already superseded"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20261105203734.979168-2-mario.behn@gmail.com>
References: <20261105203734.979168-2-mario.behn@gmail.com>
TO: Mario Behn <mario.behn@gmail.com>
TO: Mark Brown <broonie@kernel.org>
TO: Michal Simek <monstr@monstr.eu>
CC: linux-spi@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-kernel@vger.kernel.org
CC: Mario Behn <mario.behn@gmail.com>
Hi Mario,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v7.3]
[cannot apply to xilinx-xlnx/master broonie-spi/for-next v7.4-rc1 linus/master next-20261111]
[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/Mario-Behn/spi-zynq-qspi-read-flash-above-16-MiB-via-the-extended-address-register/20261105-213733
base: v7.3
patch link: https://lore.kernel.org/r/20261105203734.979168-2-mario.behn%40gmail.com
patch subject: [PATCH v1 1/2] spi: zynq-qspi: read flash above 16 MiB via the extended address register
:::::: branch date: 7 days ago
:::::: commit date: 7 days ago
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20261113/202611130828.KCC0t13G-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261113/202611130828.KCC0t13G-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/r/202611130828.KCC0t13G-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/spi/spi-zynq-qspi.c:575 expecting prototype for zynq_qspi_exec_mem_op(). Prototype was for zynq_qspi_exec_plain_op() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-11-13 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 0:46 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-05 20:37 [PATCH v1 0/2] spi: zynq-qspi: use a flash larger than 16 MiB Mario Behn
2026-11-05 20:37 ` [PATCH v1 1/2] spi: zynq-qspi: read flash above 16 MiB via the extended address register Mario Behn
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=202611130828.KCC0t13G-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.