public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Jason Wang <jasowang@redhat.com>,
	Leon Romanovsky <leon@kernel.org>,
	Leon Romanovsky <leonro@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the vhost tree with the dma-mapping tree
Date: Fri, 18 Jul 2025 18:12:26 +1000	[thread overview]
Message-ID: <20250718181226.6343c557@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/virtio/virtio_ring.c

between commit:

  b420b31f009f ("kmsan: convert kmsan_handle_dma to use physical addresses")

from the dma-mapping tree and commit:

  d1814d4fca2c ("virtio: rename dma helpers")

from the vhost 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.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/virtio/virtio_ring.c
index a8421dc802d6,3f86e74dd79f..000000000000
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_ring.c
@@@ -3143,17 -3240,17 +3240,17 @@@ EXPORT_SYMBOL_GPL(virtqueue_unmap_page_
   * The caller calls this to do dma mapping in advance. The DMA address can be
   * passed to this _vq when it is in pre-mapped mode.
   *
-  * return DMA address. Caller should check that by virtqueue_dma_mapping_error().
+  * return mapped address. Caller should check that by virtqueue_mapping_error().
   */
- dma_addr_t virtqueue_dma_map_single_attrs(struct virtqueue *_vq, void *ptr,
- 					  size_t size,
- 					  enum dma_data_direction dir,
- 					  unsigned long attrs)
+ dma_addr_t virtqueue_map_single_attrs(const struct virtqueue *_vq, void *ptr,
+ 				      size_t size,
+ 				      enum dma_data_direction dir,
+ 				      unsigned long attrs)
  {
- 	struct vring_virtqueue *vq = to_vvq(_vq);
+ 	const struct vring_virtqueue *vq = to_vvq(_vq);
  
- 	if (!vq->use_dma_api) {
+ 	if (!vq->use_map_api) {
 -		kmsan_handle_dma(virt_to_page(ptr), offset_in_page(ptr), size, dir);
 +		kmsan_handle_dma(virt_to_phys(ptr), size, dir);
  		return (dma_addr_t)virt_to_phys(ptr);
  	}
  

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-07-18  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  8:12 Stephen Rothwell [this message]
2025-07-20  9:28 ` linux-next: manual merge of the vhost tree with the dma-mapping tree Leon Romanovsky

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=20250718181226.6343c557@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jasowang@redhat.com \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mst@redhat.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