From: Jason Gunthorpe <jgg@ziepe.ca>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Jianxin Xiong <jianxin.xiong@intel.com>,
linux-rdma@vger.kernel.org, dri-devel@lists.freedesktop.org,
Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH v10 6/6] dma-buf: Document that dma-buf size is fixed
Date: Thu, 12 Nov 2020 09:25:14 -0400 [thread overview]
Message-ID: <20201112132514.GR244516@ziepe.ca> (raw)
In-Reply-To: <20201111163323.GP401619@phenom.ffwll.local>
On Wed, Nov 11, 2020 at 05:33:23PM +0100, Daniel Vetter wrote:
> On Tue, Nov 10, 2020 at 01:41:17PM -0800, Jianxin Xiong wrote:
> > The fact that the size of dma-buf is invariant over the lifetime of the
> > buffer is mentioned in the comment of 'dma_buf_ops.mmap', but is not
> > documented at where the info is defined. Add the missing documentation.
> >
> > Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com>
>
> Applied to drm-misc-next, thanks for your patch. For the preceeding
> dma-buf patch I'll wait for more review/acks before I apply it. Ack from
> Jason might also be good, since looks like this dma_virt_ops is only used
> in rdma.
We are likely to delete it entirely this cycle, Christoph already has
a patch series to do it:
https://patchwork.kernel.org/project/linux-rdma/list/?series=379277
So, lets just forget about it
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, dri-devel@lists.freedesktop.org,
Doug Ledford <dledford@redhat.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Christian Koenig <christian.koenig@amd.com>,
Jianxin Xiong <jianxin.xiong@intel.com>
Subject: Re: [PATCH v10 6/6] dma-buf: Document that dma-buf size is fixed
Date: Thu, 12 Nov 2020 09:25:14 -0400 [thread overview]
Message-ID: <20201112132514.GR244516@ziepe.ca> (raw)
In-Reply-To: <20201111163323.GP401619@phenom.ffwll.local>
On Wed, Nov 11, 2020 at 05:33:23PM +0100, Daniel Vetter wrote:
> On Tue, Nov 10, 2020 at 01:41:17PM -0800, Jianxin Xiong wrote:
> > The fact that the size of dma-buf is invariant over the lifetime of the
> > buffer is mentioned in the comment of 'dma_buf_ops.mmap', but is not
> > documented at where the info is defined. Add the missing documentation.
> >
> > Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com>
>
> Applied to drm-misc-next, thanks for your patch. For the preceeding
> dma-buf patch I'll wait for more review/acks before I apply it. Ack from
> Jason might also be good, since looks like this dma_virt_ops is only used
> in rdma.
We are likely to delete it entirely this cycle, Christoph already has
a patch series to do it:
https://patchwork.kernel.org/project/linux-rdma/list/?series=379277
So, lets just forget about it
Jason
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-12 13:25 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 21:41 [PATCH v10 0/6] RDMA: Add dma-buf support Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-10 21:41 ` [PATCH v10 1/6] RDMA/umem: Support importing dma-buf as user memory region Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-13 0:30 ` Jason Gunthorpe
2020-11-13 0:30 ` Jason Gunthorpe
2020-11-13 3:30 ` Xiong, Jianxin
2020-11-13 3:30 ` Xiong, Jianxin
2020-11-13 12:49 ` Jason Gunthorpe
2020-11-13 12:49 ` Jason Gunthorpe
2020-11-10 21:41 ` [PATCH v10 2/6] RDMA/core: Add device method for registering dma-buf based " Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-10 21:41 ` [PATCH v10 3/6] RDMA/uverbs: Add uverbs command for dma-buf based MR registration Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-13 0:33 ` Jason Gunthorpe
2020-11-13 0:33 ` Jason Gunthorpe
2020-11-13 4:02 ` Xiong, Jianxin
2020-11-13 4:02 ` Xiong, Jianxin
2020-11-10 21:41 ` [PATCH v10 4/6] RDMA/mlx5: Support dma-buf based userspace memory region Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-13 0:39 ` Jason Gunthorpe
2020-11-13 0:39 ` Jason Gunthorpe
2020-11-13 3:51 ` Xiong, Jianxin
2020-11-13 3:51 ` Xiong, Jianxin
2020-11-13 13:06 ` Jason Gunthorpe
2020-11-13 13:06 ` Jason Gunthorpe
2020-11-13 17:28 ` Xiong, Jianxin
2020-11-13 17:28 ` Xiong, Jianxin
2020-11-10 21:41 ` [PATCH v10 5/6] dma-buf: Reject attach request from importers that use dma_virt_ops Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-10 21:41 ` [PATCH v10 6/6] dma-buf: Document that dma-buf size is fixed Jianxin Xiong
2020-11-10 21:41 ` Jianxin Xiong
2020-11-11 16:33 ` Daniel Vetter
2020-11-11 16:33 ` Daniel Vetter
2020-11-12 13:25 ` Jason Gunthorpe [this message]
2020-11-12 13:25 ` Jason Gunthorpe
2020-11-13 20:41 ` Daniel Vetter
2020-11-13 20:41 ` Daniel Vetter
2020-11-13 0:42 ` [PATCH v10 0/6] RDMA: Add dma-buf support Jason Gunthorpe
2020-11-13 0:42 ` Jason Gunthorpe
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=20201112132514.GR244516@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dledford@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jianxin.xiong@intel.com \
--cc=leon@kernel.org \
--cc=linux-rdma@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 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.