public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Johannes Berg <johannes@sipsolutions.net>
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 09:57:02 -0800	[thread overview]
Message-ID: <45D1FBEE.2010505@oracle.com> (raw)
In-Reply-To: <1171389259.10344.62.camel@johannes.berg>

Johannes Berg wrote:
> 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.

Uh, please try one more thing.  Delete the '*' line between
 * struct pm_ops - Callbacks ...

and the struct members list and retest that.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-02-13 17:57 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
2007-02-13 17:57         ` Randy Dunlap [this message]
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=45D1FBEE.2010505@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@osdl.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    /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