From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: "Karicheri, Muralidharan" <m-karicheri2@ti.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Help in adding documentation
Date: Wed, 18 Nov 2009 17:47:58 -0200 [thread overview]
Message-ID: <4B044F6E.8010008@infradead.org> (raw)
In-Reply-To: <A69FA2915331DC488A831521EAE36FE401559C60B9@dlee06.ent.ti.com>
Karicheri, Muralidharan wrote:
> Mauro,
>
> Is there specific way to create patch for this documentation?
>
> Can I just do following commands and send one patch?
>
> Baseline tree - v4l-dvb-base (original)
> Changed tree - v4l-dvb-change
>
> diff -uNr v4l-dvb-base v4l-dvb-change >media-doc.patch
Well, this should work, however the better way is to clone the
tree with hg, modify it and do
hg diff >media-doc.patch
Mercurial is not that different from cvs, svn or git, so you can
also commit patches there and later export them for sending via email.
>
> Murali Karicheri
> Software Design Engineer
> Texas Instruments Inc.
> Germantown, MD 20874
> phone: 301-407-9583
> email: m-karicheri2@ti.com
>
>> -----Original Message-----
>> From: Mauro Carvalho Chehab [mailto:mchehab@infradead.org]
>> Sent: Tuesday, November 17, 2009 12:58 PM
>> To: Karicheri, Muralidharan
>> Cc: Hans Verkuil; linux-media@vger.kernel.org
>> Subject: Re: Help in adding documentation
>>
>> Karicheri, Muralidharan escreveu:
>>> Mauro,
>>>
>>> Thanks for your reply. I made progress after my email. My new file
>>> is being processed by Makefile now. I have some issues with some
>>> tags.
>>>
>>>> This probably means that videodev2.h has it defined, while you didn't
>> have
>>> Do you mean videodev2.h.xml? I see there videodev2.h under linux/include.
>> Do I need to copy my latest videodev2.h to that directory?
>>
>> videodev2.h.xml is generated automatically by Makefile, from videodev2.h.
>>
>> Basically, Makefile scripts will parse it, search for certain
>> structs/enums/ioctls and
>> generate videodev2.h.xml.
>>
>> What happens is that you likely declared the presets enum on videodev2.h,
>> and the
>> enum got detected, producing a <linkend> tag. However, as you didn't define
>> the
>> reference ID for that tag on your xml file, you got an error.
>>>> the
>>>> link id created at the xml file you've created.
>>>>
>>>> You probably need a tag like:
>>>>
>>>> <table pgwide="1" frame="none" id="v4l2-dv-enum-presets">
>>>> <!-- your enum table -->
>>>> </table>
>>>>
>>>>
>>>> Cheers,
>>>> Mauro
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-media"
>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-11-18 19:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 16:00 Help in adding documentation Karicheri, Muralidharan
2009-11-17 16:28 ` Mauro Carvalho Chehab
2009-11-17 16:58 ` Karicheri, Muralidharan
2009-11-17 17:58 ` Mauro Carvalho Chehab
2009-11-17 23:29 ` Karicheri, Muralidharan
2009-11-18 7:04 ` Mauro Carvalho Chehab
2009-11-18 7:19 ` Hans Verkuil
2009-11-18 7:24 ` Mauro Carvalho Chehab
2009-11-18 7:32 ` Hans Verkuil
2009-11-19 16:23 ` Karicheri, Muralidharan
2009-11-19 16:26 ` Karicheri, Muralidharan
2009-11-19 17:01 ` Karicheri, Muralidharan
2009-11-20 11:51 ` Hans Verkuil
2009-11-18 18:19 ` Karicheri, Muralidharan
2009-11-18 19:47 ` Mauro Carvalho Chehab [this message]
2009-11-18 20:41 ` Karicheri, Muralidharan
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 15:57 Karicheri, Muralidharan
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=4B044F6E.8010008@infradead.org \
--to=mchehab@infradead.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m-karicheri2@ti.com \
/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