From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PATCHES FOR 2.6.37] V4L documentation fixes
Date: Wed, 22 Sep 2010 16:42:03 -0300 [thread overview]
Message-ID: <4C9A5C0B.3040506@redhat.com> (raw)
In-Reply-To: <201009150923.50132.hverkuil@xs4all.nl>
Em 15-09-2010 04:23, Hans Verkuil escreveu:
> The following changes since commit 57fef3eb74a04716a8dd18af0ac510ec4f71bc05:
> Richard Zidlicky (1):
> V4L/DVB: dvb: fix smscore_getbuffer() logic
>
> are available in the git repository at:
>
> ssh://linuxtv.org/git/hverkuil/v4l-dvb.git misc2
>
> Hans Verkuil (6):
> V4L Doc: removed duplicate link
This doesn't seem right. the entry for V4L2-PIX-FMT-BGR666 seems to be duplicated.
We should remove the duplication, instead of just dropping the ID.
> V4L Doc: fix DocBook syntax errors.
> V4L Doc: document V4L2_CAP_RDS_OUTPUT capability.
> V4L Doc: correct the documentation for VIDIOC_QUERYMENU.
Applied, thanks.
> V4L Doc: rewrite the Device Naming section
The new text is incomplete, as it assumes only the old non-dynamic device node
creation. Also, some distros actually create /dev/v4l, as recommended. IMHO, we
need to improve this section, proposing a better way to name devices. This may
be an interesting theme for this year's LPC.
> V4L Doc: clarify the V4L spec.
This is a mix of several changes on the same patch. I want to do comments about it,
but no time right now to write an email about that. It is a way harder to comment
Docbook changes than patches, as the diff output is not user-friendly.
I'll postpone this patch for a better analysis.
I don't want to postpone the DocBook correction patches due to that, so I'm applying
the patches I'm ok.
Cheers,
Mauro
next prev parent reply other threads:[~2010-09-22 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 7:23 [GIT PATCHES FOR 2.6.37] V4L documentation fixes Hans Verkuil
2010-09-22 19:42 ` Mauro Carvalho Chehab [this message]
2010-09-22 20:06 ` Hans Verkuil
2010-09-22 20:19 ` Hans Verkuil
2010-09-22 21:17 ` Mauro Carvalho Chehab
2010-09-23 5:47 ` Hans Verkuil
2010-09-23 9:02 ` Paulo Assis
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=4C9A5C0B.3040506@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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.