From: Christoph Hellwig <hch@lst.de>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Tomasz Figa <tfiga@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Ricardo Ribalda <ribalda@chromium.org>,
Sergey Senozhatsky <senozhatsky@google.com>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Robin Murphy <robin.murphy@arm.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 6/7] dma-iommu: implement ->alloc_noncontiguous
Date: Mon, 1 Mar 2021 09:11:51 +0100 [thread overview]
Message-ID: <20210301081151.GA28023@lst.de> (raw)
In-Reply-To: <YDyfo9OKkRHxd89O@google.com>
On Mon, Mar 01, 2021 at 05:02:43PM +0900, Sergey Senozhatsky wrote:
> > I plan to resend the whole series with the comments very soon.
>
> Oh, OK.
>
> I thought the series was in linux-next already so a single patch
> would do.
It was, with an emphasys on was. I hadn't realized I need an ack
from Laurent for uvcvideo, and he didn't have time to review it by the
time we noticed. So I'll repost it with him in the receipients list and
the small fixups accumulated now that -rc1 is out.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Sergey Senozhatsky <senozhatsky@google.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 6/7] dma-iommu: implement ->alloc_noncontiguous
Date: Mon, 1 Mar 2021 09:11:51 +0100 [thread overview]
Message-ID: <20210301081151.GA28023@lst.de> (raw)
In-Reply-To: <YDyfo9OKkRHxd89O@google.com>
On Mon, Mar 01, 2021 at 05:02:43PM +0900, Sergey Senozhatsky wrote:
> > I plan to resend the whole series with the comments very soon.
>
> Oh, OK.
>
> I thought the series was in linux-next already so a single patch
> would do.
It was, with an emphasys on was. I hadn't realized I need an ack
from Laurent for uvcvideo, and he didn't have time to review it by the
time we noticed. So I'll repost it with him in the receipients list and
the small fixups accumulated now that -rc1 is out.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-03-01 8:13 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 9:51 add a new dma_alloc_noncontiguous API v2 Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 1/7] dma-mapping: remove the {alloc,free}_noncoherent methods Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 2/7] dma-mapping: add a dma_mmap_pages helper Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 3/7] dma-mapping: refactor dma_{alloc,free}_pages Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 4/7] dma-mapping: add a dma_alloc_noncontiguous API Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-16 18:55 ` Robin Murphy
2021-02-16 18:55 ` Robin Murphy
2021-03-01 8:09 ` Christoph Hellwig
2021-03-01 8:09 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 5/7] dma-iommu: refactor iommu_dma_alloc_remap Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 6/7] dma-iommu: implement ->alloc_noncontiguous Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-16 8:14 ` Tomasz Figa
2021-02-16 8:14 ` Tomasz Figa
2021-02-16 8:49 ` Christoph Hellwig
2021-02-16 8:49 ` Christoph Hellwig
2021-03-01 7:17 ` Sergey Senozhatsky
2021-03-01 7:17 ` Sergey Senozhatsky
2021-03-01 7:21 ` Christoph Hellwig
2021-03-01 7:21 ` Christoph Hellwig
2021-03-01 8:02 ` Sergey Senozhatsky
2021-03-01 8:02 ` Sergey Senozhatsky
2021-03-01 8:11 ` Christoph Hellwig [this message]
2021-03-01 8:11 ` Christoph Hellwig
2021-02-02 9:51 ` [PATCH 7/7] media: uvcvideo: Use dma_alloc_noncontiguos API Christoph Hellwig
2021-02-02 9:51 ` Christoph Hellwig
2021-02-04 7:39 ` Hillf Danton
2021-02-07 18:48 ` add a new dma_alloc_noncontiguous API v2 Christoph Hellwig
2021-02-07 18:48 ` Christoph Hellwig
2021-02-08 11:33 ` Tomasz Figa
2021-02-08 11:33 ` Tomasz Figa
2021-02-09 8:22 ` Christoph Hellwig
2021-02-09 8:29 ` Ricardo Ribalda
2021-02-09 8:29 ` Ricardo Ribalda
2021-02-09 14:46 ` Ricardo Ribalda
2021-02-09 14:46 ` Ricardo Ribalda
2021-02-09 17:02 ` Christoph Hellwig
2021-02-11 9:08 ` Ricardo Ribalda
2021-02-11 9:08 ` Ricardo Ribalda
2021-02-11 13:06 ` Christoph Hellwig
2021-02-11 13:06 ` Christoph Hellwig
2021-02-11 13:20 ` Ricardo Ribalda
2021-02-11 13:20 ` Ricardo Ribalda
2021-02-11 13:55 ` Laurent Pinchart
2021-02-11 13:55 ` Laurent Pinchart
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=20210301081151.GA28023@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=robin.murphy@arm.com \
--cc=senozhatsky@google.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tfiga@chromium.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.