From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 3/3] [media] DocBook: Add rules to auto-generate some media docbook
Date: Wed, 01 Jun 2011 18:34:17 -0300 [thread overview]
Message-ID: <4DE6B059.8080308@redhat.com> (raw)
In-Reply-To: <20110601090126.0fe77a14.rdunlap@xenotime.net>
Em 01-06-2011 13:01, Randy Dunlap escreveu:
> On Wed, 01 Jun 2011 07:52:33 -0300 Mauro Carvalho Chehab wrote:
>
>> Hi Randy,
>>
>> Em 26-05-2011 00:10, Randy Dunlap escreveu:
>>> On Wed, 25 May 2011 12:26:42 -0300 Mauro Carvalho Chehab wrote:
>>>
>>>> Auto-generate the videodev2.h.xml,frontend.h.xml and the indexes.
>>>>
>>>> Some logic at the Makefile helps us to identify when a symbol is missing,
>>>> like for example:
>>>>
>>>> Error: no ID for constraint linkend: V4L2-PIX-FMT-JPGL.
>>>
>>>
>>> a. Still get that message.. is that OK?
>>>
>>> b. In the generated index.html file, "media" is listed first, but it should be
>>> listed in alphabetical order, not first.
>>>
>>> c. The generated files are (hidden) in .tmpmedia/
>>>
>>> d. The link from the top-level index.html file to "media" is to
>>> media/index.html, but the file is actually in .tmpmedia/media/index.html
>>>
>>> e. patches 1/3 and 2/3 are OK.
>>>
>>>
>>> Please build docs with and without using "O=builddir" and test that.
>>>
>>> I'm looking over the generated output now and will let you know if I see
>>> any other problems.
>>
>> Fixed the pointed issues. I also moved the media-specific stuff into another
>> Makefile. I opted to include it into the DocBook Makefile, as otherwise, I would
>> need to duplicate the xml conversion stuff into the media/Makefile.
>
> Sounds good. Thanks.
>
>> Patch is enclosed.
>
> It will probably be a few days before I test this again,
> so just merge it when you are ready...
Thanks for your review. I'll add it to my to my -next tree today. It is probably
ok to wait for 3.1 merge window before merging it upstream. Just merging it at the
development tree will help us to track troubles at the API changes.
Thanks,
Mauro
prev parent reply other threads:[~2011-06-01 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96c3a1277523b929bd27f5d68d5f40e2a0e5bdf3.1306337174.git.mchehab@redhat.com>
2011-05-25 15:26 ` [PATCH 2/3] [media] add V4L2-PIX-FMT-SRGGB12 & friends to docbook Mauro Carvalho Chehab
2011-05-25 15:26 ` [PATCH 3/3] [media] DocBook: Add rules to auto-generate some media docbook Mauro Carvalho Chehab
2011-05-26 3:10 ` Randy Dunlap
2011-06-01 10:52 ` Mauro Carvalho Chehab
2011-06-01 16:01 ` Randy Dunlap
2011-06-01 21:34 ` Mauro Carvalho Chehab [this message]
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=4DE6B059.8080308@redhat.com \
--to=mchehab@redhat.com \
--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