From: Christoph Hellwig <hch@lst.de>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Sergey Senozhatsky <senozhatsky@google.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 6/6] media: uvcvideo: Use dma_alloc_noncontiguous API
Date: Mon, 15 Mar 2021 11:04:25 +0100 [thread overview]
Message-ID: <20210315100424.GB3305@lst.de> (raw)
In-Reply-To: <20210312235521.1408503-1-ribalda@chromium.org>
Thanks, with all the reviews in I've applied the series to the
dma-mapping tree for 5.13.
This will eventually become a stable baseline branch for the v4l work
and the mips drm driver that needs dma_mmap_pages, but I'd like to wait
a bit for any issues to pop up in linux-next first.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Christoph Hellwig <hch@lst.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tfiga@chromium.org>,
Sergey Senozhatsky <senozhatsky@google.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v4 6/6] media: uvcvideo: Use dma_alloc_noncontiguous API
Date: Mon, 15 Mar 2021 11:04:25 +0100 [thread overview]
Message-ID: <20210315100424.GB3305@lst.de> (raw)
In-Reply-To: <20210312235521.1408503-1-ribalda@chromium.org>
Thanks, with all the reviews in I've applied the series to the
dma-mapping tree for 5.13.
This will eventually become a stable baseline branch for the v4l work
and the mips drm driver that needs dma_mmap_pages, but I'd like to wait
a bit for any issues to pop up in linux-next first.
next prev parent reply other threads:[~2021-03-15 10:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 23:55 [PATCH v4 6/6] media: uvcvideo: Use dma_alloc_noncontiguous API Ricardo Ribalda
2021-03-12 23:55 ` Ricardo Ribalda
2021-03-15 7:30 ` Ricardo Ribalda
2021-03-15 7:30 ` Ricardo Ribalda
2021-03-15 7:34 ` Christoph Hellwig
2021-03-15 7:34 ` Christoph Hellwig
2021-03-15 7:35 ` Ricardo Ribalda
2021-03-15 7:35 ` Ricardo Ribalda
2021-03-15 10:04 ` Christoph Hellwig [this message]
2021-03-15 10:04 ` Christoph Hellwig
2021-03-19 13:05 ` Ricardo Ribalda
2021-03-19 13:05 ` Ricardo Ribalda
2021-03-19 13:10 ` Christoph Hellwig
2021-03-19 13:10 ` Christoph Hellwig
2021-03-19 13:10 ` Ricardo Ribalda
2021-03-19 13:10 ` Ricardo Ribalda
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=20210315100424.GB3305@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=robin.murphy@arm.com \
--cc=senozhatsky@google.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 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.