From: Alex Williamson <alex.williamson@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "open list:VFIO MEDIATED DEVICE DRIVERS" <kvm@vger.kernel.org>,
airlied@linux.ie, daniel.vetter@ffwll.ch,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Kirti Wankhede <kwankhede@nvidia.com>,
linux-next@vger.kernel.org, christian.koenig@amd.com
Subject: Re: [PATCH 2/2] sample/mdev/mbochs: add mbochs_kunmap_dmabuf
Date: Wed, 27 Jun 2018 09:55:48 +0800 [thread overview]
Message-ID: <20180627095548.7c8735f2@t450s.home> (raw)
In-Reply-To: <20180626073233.kievmdagzgtxs7j7@sirius.home.kraxel.org>
On Tue, 26 Jun 2018 09:32:33 +0200
Gerd Hoffmann <kraxel@redhat.com> wrote:
> > > .map = mbochs_kmap_dmabuf,
> > > + .unmap = mbochs_kunmap_dmabuf,
> > > .mmap = mbochs_mmap_dmabuf,
> > > };
> > >
> >
> > Is this a fix for v4.18?
>
> Yes.
>
> > AFAICT, the kmap_atomic removal is only in
> > next, not yet upstream and hopefully includes this sample driver before
> > hitting mainline. Should we therefore have a v4.18-rc based patch for
> > this to include before v4.18 to resolve this?
>
> The kmap_atomic interface will be removed in 4.19 because nobody uses
> it, so dropping the mbochs implementation already in 4.18 should not
> cause any issues.
>
> So just queue both for 4.18 would be the easiest way do deal with the
> dependency I think.
Ok, so I'll drop the fixes tag and apply both to my for-linus branch
for v4.18 and then Christian won't need to include it for the v4.19
patch. Thanks,
Alex
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-27 1:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 6:44 [PATCH 1/2] sample/mdev/mbochs: remove mbochs_kmap_atomic_dmabuf Gerd Hoffmann
2018-06-25 6:44 ` [PATCH 2/2] sample/mdev/mbochs: add mbochs_kunmap_dmabuf Gerd Hoffmann
2018-06-26 7:20 ` Alex Williamson
2018-06-26 7:32 ` Gerd Hoffmann
2018-06-27 1:55 ` Alex Williamson [this message]
2018-06-25 15:43 ` [PATCH 1/2] sample/mdev/mbochs: remove mbochs_kmap_atomic_dmabuf Koenig, Christian
2018-06-26 7:16 ` Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 7:33 [PATCH 2/2] sample/mdev/mbochs: add mbochs_kunmap_dmabuf Koenig, Christian
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=20180627095548.7c8735f2@t450s.home \
--to=alex.williamson@redhat.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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