linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	"linux-doc\@vger.kernel.org" <linux-doc@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] kernel-doc: fix declaration type determination
Date: Thu, 18 Oct 2018 12:14:53 +0300	[thread overview]
Message-ID: <87va5zipki.fsf@intel.com> (raw)
In-Reply-To: <640b26f4-a6fa-ffbc-c866-ea03de4f79a5@infradead.org>

On Wed, 17 Oct 2018, Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Make declaration type determination more robust.
>
> When scripts/kernel-doc is deciding if some kernel-doc notation
> contains an enum, a struct, a union, a typedef, or a function,
> it does a pattern match on the beginning of the string, looking
> for a match with one of "struct", "union", "enum", or "typedef",
> and otherwise defaults to a function declaration type.
> However, if a function or a function-like macro has a name that
> begins with "struct" (e.g., struct_size()), then kernel-doc
> incorrectly decides that this is a struct declaration.
>
> Fix this by looking for the declaration type keywords having an
> ending word boundary (\b), so that "struct_size" will not match
> a struct declaration.

My perl is all cargo cult, so can't really review, but based on the
description this is what should be done,

Acked-by: Jani Nikula <jani.nikula@intel.com>

> I compared lots of html before/after output from core-api, driver-api,
> and networking.  There were no differences in any of the files that
> I checked.

I used to do diff -r on pre and post change clean documentation builds
to verify this type of stuff.

BR,
Jani.

>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Kees Cook <keescook@chromium.org>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
>  scripts/kernel-doc |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> --- lnx-419-rc8.orig/scripts/kernel-doc
> +++ lnx-419-rc8/scripts/kernel-doc
> @@ -1904,13 +1904,13 @@ sub process_name($$) {
>  	    ++$warnings;
>  	}
>  
> -	if ($identifier =~ m/^struct/) {
> +	if ($identifier =~ m/^struct\b/) {
>  	    $decl_type = 'struct';
> -	} elsif ($identifier =~ m/^union/) {
> +	} elsif ($identifier =~ m/^union\b/) {
>  	    $decl_type = 'union';
> -	} elsif ($identifier =~ m/^enum/) {
> +	} elsif ($identifier =~ m/^enum\b/) {
>  	    $decl_type = 'enum';
> -	} elsif ($identifier =~ m/^typedef/) {
> +	} elsif ($identifier =~ m/^typedef\b/) {
>  	    $decl_type = 'typedef';
>  	} else {
>  	    $decl_type = 'function';
>
>

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2018-10-18  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  4:07 [PATCH] kernel-doc: fix declaration type determination Randy Dunlap
2018-10-18  9:14 ` Jani Nikula [this message]
2018-10-18 18:21 ` Jonathan Corbet

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=87va5zipki.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).