From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH v2] kernel-doc: include struct short description in title output
Date: Tue, 13 Feb 2007 20:43:38 +0100 [thread overview]
Message-ID: <1171395818.10344.126.camel@johannes.berg> (raw)
In-Reply-To: <20070213113522.8490ddaf.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
On Tue, 2007-02-13 at 11:35 -0800, Randy Dunlap wrote:
> > Yup, that fixes it for structs. I guess I forgot to mention this earlier
> > because I didn't notice it until now... the same bug exists for
> > functions as well.
>
> updated patch. Thanks.
Thanks, works great.
> ---
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Output of a function or struct in html mode needs to include the short
> description from the function/struct name line in the output title line.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
So if anyone cares:
Acked-by: Johannes Berg <johannes@sipsolutions.net>
> ---
> scripts/kernel-doc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-2.6.20-git7.orig/scripts/kernel-doc
> +++ linux-2.6.20-git7/scripts/kernel-doc
> @@ -452,7 +452,7 @@ sub output_struct_html(%) {
> my %args = %{$_[0]};
> my ($parameter);
>
> - print "<h2>".$args{'type'}." ".$args{'struct'}."</h2>\n";
> + print "<h2>".$args{'type'}." ".$args{'struct'}. " - " .$args{'purpose'}."</h2>\n";
> print "<b>".$args{'type'}." ".$args{'struct'}."</b> {<br>\n";
> foreach $parameter (@{$args{'parameterlist'}}) {
> if ($parameter =~ /^#/) {
> @@ -498,8 +498,8 @@ sub output_function_html(%) {
> my %args = %{$_[0]};
> my ($parameter, $section);
> my $count;
> - print "<h2>Function</h2>\n";
>
> + print "<h2>" .$args{'function'}." - ".$args{'purpose'}."</h2>\n";
> print "<i>".$args{'functiontype'}."</i>\n";
> print "<b>".$args{'function'}."</b>\n";
> print "(";
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-02-13 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 19:10 [PATCH] " Randy Dunlap
2007-02-13 19:18 ` Johannes Berg
2007-02-13 19:35 ` [PATCH v2] " Randy Dunlap
2007-02-13 19:43 ` Johannes Berg [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=1171395818.10344.126.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®