All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Frank Li <Frank.Li@nxp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Richard Leitner <richard.leitner@linux.dev>
Subject: linux-next: manual merge of the spi tree with the origin tree
Date: Mon, 19 Oct 2026 17:10:59 +0100	[thread overview]
Message-ID: <atZBEx63Bi2iNAEt@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]

Hi all,

Today's linux-next merge of the spi tree got a conflict in:

  drivers/spi/spi-imx.c

between commit:

  59eb22641f0c5 ("spi: imx: fix slab corruption from undersized DMA bounce buffers")

from the origin tree and commit:

  853de617c4a62 ("spi: use dmaengine_get_dma_device() instead of chan->device->dev")

from the spi tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc drivers/spi/spi-imx.c
index 3851c50dbe314,868f963e61371..0000000000000
--- a/drivers/spi/spi-imx.c
+++ b/drivers/spi/spi-imx.c
@@@ -1921,9 -1919,8 +1921,9 @@@ static int spi_imx_dma_package_transfer
  		return ret;
  
  	/* Trim the DMA RX buffer and copy the actual data to rx_buf */
- 	dma_sync_single_for_cpu(controller->dma_rx->device->dev, dma_data->dma_rx_addr,
+ 	dma_sync_single_for_cpu(dmaengine_get_dma_device(controller->dma_rx), dma_data->dma_rx_addr,
 -				dma_data->dma_len, DMA_FROM_DEVICE);
 +				DMA_CACHE_ALIGNED_LEN(dma_data->dma_len),
 +				DMA_FROM_DEVICE);
  	spi_imx_dma_rx_data_handle(spi_imx, dma_data, transfer->rx_buf + spi_imx->rx_offset,
  				   word_delay);
  	spi_imx->rx_offset += dma_data->data_len;

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

                 reply	other threads:[~2026-10-19 16:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=atZBEx63Bi2iNAEt@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=richard.leitner@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.