public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] WIP: cbfs: Add docbook template
Date: Fri, 2 Nov 2012 04:39:11 +0100	[thread overview]
Message-ID: <201211020439.11993.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ14KMOd1_3baCJTS2e435yBXuOyJausTod6AofuFrOvTw@mail.gmail.com>

Dear Simon Glass,

> Hi Marek,
> 
> On Wed, Oct 31, 2012 at 4:39 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Simon Glass,
> > 
> >> This adds a docbook template for fs, and makes CBFS use it.
> >> 
> >> Problems (advise please as I have enough 500pp books in my bookshelf):
> > 
> >> 1. It requires the function names to be repeated. I would like to do this:
> > Repeating function names is good, you can be sure what the comment is
> > associated with.
> 
> Hmmm, well I already know that, since the comment appears immediately
> above the function...

At the time of writing, yes. But some adjustment of code might mess that up.

> > [...]
> > 
> >> 2. It will not accept the doxygen @param style for parameters:
> > It's not doxygen, sorry. Read [1].
> 
> Yes, I was rather hoping there was an easy way to fix these two
> things. Never mind.

I'd say there is, but let's fix it in Linux kernel too. Actually, I have a pile 
of patches for Linux kernel's documentation, but it's hard to get any 
documentation patches in :-C

> > btw. I'd like some kind of @return, but maybe describing the return value
> > in comment is enough.
> 
> Maybe, but it's nice to be explicit. The return value is at least as
> important as the parameters, and they are called out.

I agree (!).

> Anyway I will rev the patch with the above in mind.
[...]

btw. It'd be nice to be able to patch the upstream (linux's) kerneldoc :-(

Best regards,
Marek Vasut

      reply	other threads:[~2012-11-02  3:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 22:27 [U-Boot] [PATCH] WIP: cbfs: Add docbook template Simon Glass
2012-10-31 23:39 ` Marek Vasut
2012-11-02  2:23   ` Simon Glass
2012-11-02  3:39     ` Marek Vasut [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=201211020439.11993.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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