From: Sakari Ailus <sakari.ailus@iki.fi>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Pawel Osciak <pawel@osciak.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: vb2: unify calling of set_page_dirty_lock
Date: Tue, 10 Oct 2017 11:54:46 +0300 [thread overview]
Message-ID: <20171010085446.n3yrr5whcv7lsbpr@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <8c775a5d-e42a-761b-e5ef-6dee93d7f476@samsung.com>
On Tue, Oct 10, 2017 at 10:01:36AM +0200, Marek Szyprowski wrote:
> Hi Stanimir,
>
> On 2017-10-10 09:42, Stanimir Varbanov wrote:
> > Marek,
> >
> > Any comments?
>
> Oh, I thought that this one has been already merged. If not (yet),
> here is my ack.
>
> > On 08/29/2017 02:26 PM, Stanimir Varbanov wrote:
> > > Currently videobuf2-dma-sg checks for dma direction for
> > > every single page and videobuf2-dc lacks any dma direction
> > > checks and calls set_page_dirty_lock unconditionally.
> > >
> > > Thus unify and align the invocations of set_page_dirty_lock
> > > for videobuf2-dc, videobuf2-sg memory allocators with
> > > videobuf2-vmalloc, i.e. the pattern used in vmalloc has been
> > > copied to dc and dma-sg.
> > >
> > > Suggested-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > > Signed-off-by: Stanimir Varbanov <stanimir.varbanov@linaro.org>
>
> Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Sakari Ailus
e-mail: sakari.ailus@iki.fi
next prev parent reply other threads:[~2017-10-10 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 11:26 [PATCH] media: vb2: unify calling of set_page_dirty_lock Stanimir Varbanov
2017-10-10 7:42 ` Stanimir Varbanov
2017-10-10 8:01 ` Marek Szyprowski
2017-10-10 8:54 ` Sakari Ailus [this message]
2017-10-10 15:40 ` Nicolas Dufresne
2017-10-15 20:40 ` Sakari Ailus
2017-10-15 23:09 ` Nicolas Dufresne
2017-10-16 11:24 ` Sakari Ailus
2017-10-17 10:14 ` Sakari Ailus
2017-10-17 14:19 ` Nicolas Dufresne
2017-10-18 8:34 ` Stanimir Varbanov
2018-03-14 0:44 ` Nicolas Dufresne
2018-03-14 1:09 ` Nicolas Dufresne
2018-03-14 2:02 ` Nicolas Dufresne
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=20171010085446.n3yrr5whcv7lsbpr@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=pawel@osciak.com \
--cc=stanimir.varbanov@linaro.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.