From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: "Christian König" <christian.koenig@amd.com>,
"Alex Williamson" <alex@shazbot.org>,
"Simona Vetter" <simona@ffwll.ch>,
"Jani Nikula" <jani.nikula@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Chia-I Wu" <olvaffe@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Kevin Tian" <kevin.tian@intel.com>,
"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Felix Kuehling" <Felix.Kuehling@amd.com>,
"Ankit Agrawal" <ankita@nvidia.com>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org, virtualization@lists.linux.dev,
intel-xe@lists.freedesktop.org, linux-rdma@vger.kernel.org,
iommu@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [PATCH v7 7/8] vfio: Permit VFIO to work with pinned importers
Date: Thu, 5 Feb 2026 10:21:11 -0400 [thread overview]
Message-ID: <20260205142111.GK2328995@ziepe.ca> (raw)
In-Reply-To: <20260205121945.GC12824@unreal>
On Thu, Feb 05, 2026 at 02:19:45PM +0200, Leon Romanovsky wrote:
> You don't need any backmerge, SHA-1 version of vfio-v6.19-rc8 tag is the
> same as in Linus's tree, so the flow is:
I'm confused what is the problem here?
From https://anongit.freedesktop.org/git/drm/drm-misc
* branch drm-misc-next -> FETCH_HEAD
$ git show FETCH_HEAD
commit 779ec12c85c9e4547519e3903a371a3b26a289de
Author: Alexander Konyukhov <Alexander.Konyukhov@kaspersky.com>
Date: Tue Feb 3 16:48:46 2026 +0300
drm/komeda: fix integer overflow in AFBC framebuffer size check
$ git merge-base FETCH_HEAD 61ceaf236115f20f4fdd7cf60f883ada1063349a
24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7
$ git describe --contains 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7
v6.19-rc6^0
$ git log --oneline 61ceaf236115f20f4fdd7cf60f883ada1063349a ^FETCH_HEAD
61ceaf236115f2 vfio: Prevent from pinned DMABUF importers to attach to VFIO DMABUF
Just pull Alex's tree, the drm-misc-next tree already has v6.19-rc6,
so all they will see is one extra patch from Alex in your PR.
No need to backmerge, this is normal git stuff and there won't be
conflicts when they merge a later Linus tag.
Jason
next prev parent reply other threads:[~2026-02-05 14:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 5:34 [PATCH v7 0/8] dma-buf: Use revoke mechanism to invalidate shared buffers Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 1/8] dma-buf: Rename .move_notify() callback to a clearer identifier Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 2/8] dma-buf: Rename dma_buf_move_notify() to dma_buf_invalidate_mappings() Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 3/8] dma-buf: Always build with DMABUF_MOVE_NOTIFY Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 4/8] vfio: Wait for dma-buf invalidation to complete Leon Romanovsky
2026-02-04 14:47 ` Alex Williamson
2026-01-31 5:34 ` [PATCH v7 5/8] dma-buf: Make .invalidate_mapping() truly optional Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 6/8] dma-buf: Add dma_buf_attach_revocable() Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 7/8] vfio: Permit VFIO to work with pinned importers Leon Romanovsky
2026-02-04 16:21 ` Christian König
2026-02-04 16:55 ` Jason Gunthorpe
2026-02-04 16:56 ` Alex Williamson
2026-02-05 9:43 ` Christian König
2026-02-05 12:19 ` Leon Romanovsky
2026-02-05 14:21 ` Jason Gunthorpe [this message]
2026-02-05 14:28 ` Christian König
2026-02-05 14:41 ` Alex Williamson
2026-02-05 14:58 ` Jason Gunthorpe
2026-02-04 17:41 ` Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 8/8] iommufd: Add dma_buf_pin() Leon Romanovsky
2026-02-02 16:04 ` [PATCH v7 0/8] dma-buf: Use revoke mechanism to invalidate shared buffers Leon Romanovsky
2026-02-04 8:16 ` Leon Romanovsky
2026-02-04 8:54 ` Christian König
2026-02-04 11:47 ` Leon Romanovsky
2026-02-04 14:49 ` Alex Williamson
2026-02-04 13:35 ` Jason Gunthorpe
2026-02-04 8:56 ` Maxime Ripard
2026-02-04 11:52 ` Leon Romanovsky
2026-02-04 12:01 ` Maxime Ripard
2026-02-04 12:13 ` Leon Romanovsky
2026-02-04 13:44 ` Maxime Ripard
2026-02-04 13:56 ` Jason Gunthorpe
2026-02-04 15:54 ` Leon Romanovsky
2026-02-05 9:09 ` Maxime Ripard
2026-02-17 8:02 ` Leon Romanovsky
2026-02-17 9:52 ` Christian König
2026-02-17 13:34 ` Leon Romanovsky
2026-02-23 18:55 ` Christian König
2026-02-24 10:31 ` 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=20260205142111.GK2328995@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@gmail.com \
--cc=alex@shazbot.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ankita@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jani.nikula@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=robin.murphy@arm.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=vivek.kasireddy@intel.com \
--cc=will@kernel.org \
/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