public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-media@vger.kernel.org
Subject: Re: [PATCH] Updated videobuf documentation
Date: Mon, 22 Feb 2010 18:52:21 -0300	[thread overview]
Message-ID: <4B82FC95.9070301@infradead.org> (raw)
In-Reply-To: <4B82F542.2030206@xenotime.net>

Randy Dunlap wrote:
> On 02/22/10 12:47, Jonathan Corbet wrote:
>> On Fri, 19 Feb 2010 04:09:19 -0200
>> Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
>>
>>> Not anymore: there's a patch that added USERPTR support for videobuf-dma-contig:
>>>
>>> commit 720b17e759a50635c429ccaa2ec3d01edb4f92d6
>>> Author: Magnus Damm <damm@igel.co.jp>
>>> Date:   Tue Jun 16 15:32:36 2009 -0700
>>>
>>>     videobuf-dma-contig: zero copy USERPTR support
>> Now *that* is a special-purpose hack.  But it's worth mentioning, so
>> I've updated the text accordingly.
>>
>>> In terms of memory types, there's a possibility that weren't mentioned: the OVERLAY mode.
>>>
>>> Maybe a small paragraph may be added just for the completeness of the doc.
>> Yeah, I try to ignore overlay whenever I can.  I've added a brief bit.
>>
>> New version of the patch attached; look better?
> 
> Looks good to me (other than a few straggling lines that end with whitespace).
> 
> Reviewed-by: Randy Dunlap <rdunlap@xenotime.net>

Seems OK to me also. I'll apply it (running a script to remove trailing whitespaces ;) )


-- 

Cheers,
Mauro

  reply	other threads:[~2010-02-22 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 17:12 [PATCH] Updated videobuf documentation Jonathan Corbet
2010-02-18 22:59 ` Randy Dunlap
2010-02-19  6:09   ` Mauro Carvalho Chehab
2010-02-22 20:47     ` Jonathan Corbet
2010-02-22 21:21       ` Randy Dunlap
2010-02-22 21:52         ` Mauro Carvalho Chehab [this message]
2010-02-22 20:38   ` Jonathan Corbet

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=4B82FC95.9070301@infradead.org \
    --to=mchehab@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-media@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox