From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Christoph Hellwig <hch@lst.de>, Tomasz Figa <tfiga@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Sergey Senozhatsky <senozhatsky@google.com>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: add a new dma_alloc_noncontiguous API v2
Date: Thu, 11 Feb 2021 15:55:30 +0200 [thread overview]
Message-ID: <YCU3UuftNEl5Bxpf@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCupVLQMbJVKrrKBJvJxHgteeVFik7LAJy5zbUi2ESwsGA@mail.gmail.com>
Hi Ricardo,
On Thu, Feb 11, 2021 at 02:20:30PM +0100, Ricardo Ribalda wrote:
> On Thu, Feb 11, 2021 at 2:06 PM Christoph Hellwig <hch@lst.de> wrote:
> > On Thu, Feb 11, 2021 at 10:08:18AM +0100, Ricardo Ribalda wrote:
> > > Hi Christoph
> > >
> > > What are your merge plans for the uvc change?
> > > http://git.infradead.org/users/hch/dma-mapping.git/commit/3dc47131f8aacc2093f68a9971d24c754e435520
> > >
> > > Are you going to remove the patch on your Merge request and then send
> > > it for review to Laurent? or merge it through your tree with a S-o-B
> > > him?
> >
> > I though I had all the ACKs to queue it up. Is that not what was
> > intended? Queueing up the API without a user is generally a bad idea.
> >
>
> I am pretty sure we need the ack from Laurent. He maintains uvc
>
> @Laurent Pinchart what are your thoughts?
I think it would have been nice to CC me on the patch in the first place
:-) I won't have time to review the series before next week at the
earliest.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Sergey Senozhatsky <senozhatsky@google.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>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: add a new dma_alloc_noncontiguous API v2
Date: Thu, 11 Feb 2021 15:55:30 +0200 [thread overview]
Message-ID: <YCU3UuftNEl5Bxpf@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCupVLQMbJVKrrKBJvJxHgteeVFik7LAJy5zbUi2ESwsGA@mail.gmail.com>
Hi Ricardo,
On Thu, Feb 11, 2021 at 02:20:30PM +0100, Ricardo Ribalda wrote:
> On Thu, Feb 11, 2021 at 2:06 PM Christoph Hellwig <hch@lst.de> wrote:
> > On Thu, Feb 11, 2021 at 10:08:18AM +0100, Ricardo Ribalda wrote:
> > > Hi Christoph
> > >
> > > What are your merge plans for the uvc change?
> > > http://git.infradead.org/users/hch/dma-mapping.git/commit/3dc47131f8aacc2093f68a9971d24c754e435520
> > >
> > > Are you going to remove the patch on your Merge request and then send
> > > it for review to Laurent? or merge it through your tree with a S-o-B
> > > him?
> >
> > I though I had all the ACKs to queue it up. Is that not what was
> > intended? Queueing up the API without a user is generally a bad idea.
> >
>
> I am pretty sure we need the ack from Laurent. He maintains uvc
>
> @Laurent Pinchart what are your thoughts?
I think it would have been nice to CC me on the patch in the first place
:-) I won't have time to review the series before next week at the
earliest.
--
Regards,
Laurent Pinchart
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-02-11 13:59 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
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 [this message]
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=YCU3UuftNEl5Bxpf@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=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=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.