From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-pm <linux-pm@lists.osdl.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] power management: no valid states w/o pm_ops + docs
Date: Tue, 13 Feb 2007 18:54:19 +0100 [thread overview]
Message-ID: <1171389259.10344.62.camel@johannes.berg> (raw)
In-Reply-To: <45D1F835.9030103@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
On Tue, 2007-02-13 at 09:41 -0800, Randy Dunlap wrote:
> >> * struct pm_ops - callbacks for managing platform-dependent suspend states
> >
> > But then the description "callbacks for ..." disappears completely in
> > the HTML output! Should I duplicate it or something?
>
> No, it's right there by the struct name (top line).
> As you have it, it shows up at the bottom, after the struct members,
> doesn't it (i.e., out of order)?
I now have:
/**
* struct pm_ops - Callbacks for managing platform dependent suspend states.
*
*... (rest kept identical)
*/
and it's not there for me (output of
./scripts/kernel-doc -html include/linux/pm.h
attached). I also get an empty "Description" section.
But yes, if I put it into the third line then it shows up in the
"Description" section which is all the way down.
I think I'll put this down to a bug in the html output (that maybe you
get to fix? :) ), I just tested text and man output now and they both
look fine as you describe.
> I would probably just indent all of them by one tab. Don't worry about
> the @verylong one.
ok.
johannes
[-- Attachment #1.2: pm.html --]
[-- Type: text/html, Size: 2115 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-02-13 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 16:26 [PATCH] power management: no valid states w/o pm_ops + docs Johannes Berg
2007-02-13 17:23 ` Randy Dunlap
2007-02-13 17:36 ` Johannes Berg
2007-02-13 17:41 ` Randy Dunlap
2007-02-13 17:54 ` Johannes Berg [this message]
2007-02-13 17:57 ` Randy Dunlap
2007-02-13 18:02 ` Johannes Berg
2007-02-13 18:03 ` Randy Dunlap
2007-02-13 18:08 ` Johannes Berg
2007-02-13 18:09 ` Johannes Berg
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=1171389259.10344.62.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=randy.dunlap@oracle.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