From: kernel test robot <lkp@intel.com>
To: "Csókás, Bence" <csokas.bence@prolan.hu>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Mark Brown" <broonie@kernel.org>,
oe-kbuild-all@lists.linux.dev,
"Varshini Rajendran" <varshini.rajendran@microchip.com>,
"Csókás, Bence" <csokas.bence@prolan.hu>
Subject: Re: [PATCH] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families
Date: Wed, 30 Oct 2024 09:20:00 +0800 [thread overview]
Message-ID: <202410300915.VPL8EQQu-lkp@intel.com> (raw)
In-Reply-To: <20241029125843.2384307-1-csokas.bence@prolan.hu>
Hi Bence,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-spi/for-next]
[also build test ERROR on soc/for-next linus/master v6.12-rc5 next-20241029]
[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/Cs-k-s-Bence/spi-atmel-quadspi-Create-atmel_qspi_ops-to-support-newer-SoC-families/20241029-210231
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
patch link: https://lore.kernel.org/r/20241029125843.2384307-1-csokas.bence%40prolan.hu
patch subject: [PATCH] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20241030/202410300915.VPL8EQQu-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241030/202410300915.VPL8EQQu-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/202410300915.VPL8EQQu-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/spi/atmel-quadspi.c: In function 'atmel_qspi_transfer':
>> drivers/spi/atmel-quadspi.c:446:68: error: 'struct spi_device' has no member named 'master'
446 | struct atmel_qspi *aq = spi_controller_get_devdata(mem->spi->master);
| ^~
vim +446 drivers/spi/atmel-quadspi.c
442
443 static int atmel_qspi_transfer(struct spi_mem *mem,
444 const struct spi_mem_op *op, u32 offset)
445 {
> 446 struct atmel_qspi *aq = spi_controller_get_devdata(mem->spi->master);
447
448 /* Skip to the final steps if there is no data */
449 if (!op->data.nbytes)
450 return atmel_qspi_wait_for_completion(aq,
451 QSPI_SR_CMD_COMPLETED);
452
453 /* Dummy read of QSPI_IFR to synchronize APB and AHB accesses */
454 (void)atmel_qspi_read(aq, QSPI_IFR);
455
456 /* Send/Receive data */
457 if (op->data.dir == SPI_MEM_DATA_IN)
458 memcpy_fromio(op->data.buf.in, aq->mem + offset,
459 op->data.nbytes);
460 else
461 memcpy_toio(aq->mem + offset, op->data.buf.out,
462 op->data.nbytes);
463
464 /* Release the chip-select */
465 atmel_qspi_write(QSPI_CR_LASTXFER, aq, QSPI_CR);
466
467 return atmel_qspi_wait_for_completion(aq, QSPI_SR_CMD_COMPLETED);
468 }
469
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-30 2:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 13:34 [PATCH] spi: atmel-quadspi: Add support for sama7g5 QSPI Tudor Ambarus
2021-12-23 13:54 ` Tudor.Ambarus
2022-04-13 12:50 ` Michael Walle
2022-04-13 13:03 ` Tudor.Ambarus
2022-05-24 9:07 ` Claudiu.Beznea
2024-10-21 12:19 ` Csókás Bence
2024-10-21 14:20 ` Tudor Ambarus
2024-10-29 12:58 ` [PATCH] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families Csókás, Bence
2024-10-30 1:20 ` 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=202410300915.VPL8EQQu-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=csokas.bence@prolan.hu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tudor.ambarus@linaro.org \
--cc=varshini.rajendran@microchip.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).