linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: bingjingc <bingjingc@synology.com>,
	viro@zeniv.linux.org.uk, jack@suse.com, jack@suse.cz,
	axboe@kernel.dk, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, cccheng@synology.com,
	robbieko@synology.com
Subject: Re: [PATCH 3/3] parser: add unsigned int parser
Date: Wed, 27 Jan 2021 19:27:30 -0800	[thread overview]
Message-ID: <2b423da0-60da-9712-b75c-3ca41ee56634@infradead.org> (raw)
In-Reply-To: <1611800401-9790-1-git-send-email-bingjingc@synology.com>

Hi,

On 1/27/21 6:20 PM, bingjingc wrote:
> From: BingJing Chang <bingjingc@synology.com>
> 
> Will be used by fs parsing options
> 
> Reviewed-by: Robbie Ko<robbieko@synology.com>
> Reviewed-by: Chung-Chiang Cheng <cccheng@synology.com>
> Signed-off-by: BingJing Chang <bingjingc@synology.com>
> ---
>  fs/isofs/inode.c       | 16 ++--------------
>  fs/udf/super.c         | 16 ++--------------
>  include/linux/parser.h |  1 +
>  lib/parser.c           | 22 ++++++++++++++++++++++
>  4 files changed, 27 insertions(+), 28 deletions(-)

[snip]

> diff --git a/lib/parser.c b/lib/parser.c
> index f5b3e5d..2ec9c4f 100644
> --- a/lib/parser.c
> +++ b/lib/parser.c
> @@ -189,6 +189,28 @@ int match_int(substring_t *s, int *result)
>  EXPORT_SYMBOL(match_int);
>  
>  /**
> + * match_uint: - scan a decimal representation of an integer from a substring_t

This shows us that all of the kernel-doc for functions in
lib/parser.c is formatted incorrectly.

The above should be:

 * match_uint - scan a decimal representation of an integer from a substring_t

i.e., drop the ':' only on the function name lines, for all functions in
this source file.


If you don't want to do that, I'll plan to do it.


> + * @s: substring_t to be scanned
> + * @result: resulting integer on success
> + *
> + * Description: Attempts to parse the &substring_t @s as a decimal integer. On
> + * success, sets @result to the integer represented by the string and returns 0.
> + * Returns -ENOMEM, -EINVAL, or -ERANGE on failure.
> + */
> +int match_uint(substring_t *s, unsigned int *result)
> +{
> +	int err = -ENOMEM;
> +	char *buf = match_strdup(s);
> +
> +	if (buf) {
> +		err = kstrtouint(buf, 10, result);
> +		kfree(buf);
> +	}
> +	return err;
> +}
> +EXPORT_SYMBOL(match_uint);
> +
> +/**
>   * match_u64: - scan a decimal representation of a u64 from
>   *                  a substring_t

ditto.

>   * @s: substring_t to be scanned
> 


thanks.
-- 
~Randy


  reply	other threads:[~2021-01-28  3:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  2:20 [PATCH 3/3] parser: add unsigned int parser bingjingc
2021-01-28  3:27 ` Randy Dunlap [this message]
2021-01-28  8:32 ` Miklos Szeredi
     [not found]   ` <939d2196-8468-4d93-b976-70f3d8ac83de@Mail>
2021-01-29  6:00     ` bingjing chang

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=2b423da0-60da-9712-b75c-3ca41ee56634@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=bingjingc@synology.com \
    --cc=cccheng@synology.com \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robbieko@synology.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).