From: bingjing chang <bxxxjxxg@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.com>,
Jan Kara <jack@suse.cz>, Jens Axboe <axboe@kernel.dk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
cccheng@synology.com, robbieko@synology.com,
Matthew Wilcox <willy@infradead.org>,
bingjingc <bingjingc@synology.com>
Subject: Re: [PATCH v2 1/3] parser: add unsigned int parser
Date: Fri, 29 Jan 2021 14:07:46 +0800 [thread overview]
Message-ID: <CAMmgxWEm-yLzxjFrnvjjtDMtim2FDrqxJQucgs40nBSW6Hj_1Q@mail.gmail.com> (raw)
In-Reply-To: <6862f3e8-5eb6-4364-a05e-d4ad23d1d37d@Mail>
Hi Randy,
Thank you for talking to me the correct kernel-doc format. :)
I also split the cleanup of kernel doc comments into an independent
patch due to Jan's comments and submitted it. Thank you.
bingjingc <bingjingc@synology.com> 於 2021年1月29日 週五 下午1:51寫道:
>
> [loop bxxxjxxg@gmail.com] in order to reply in plain-text
> Randy Dunlap <rdunlap@infradead.org> 於 2021-01-29 05:26 寫道:
>
> On 1/27/21 11:13 PM, bingjingc wrote:
> > From: BingJing Chang <bingjingc@synology.com>
> >
> > Will be used by fs parsing options & fix kernel-doc typos
> >
> > Reviewed-by: Robbie Ko<robbieko@synology.com>
> > Reviewed-by: Chung-Chiang Cheng <cccheng@synology.com>
> > Reviewed-by: Matthew Wilcox <willy@infradead.org>
> > Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>
> You should drop my Reviewed-by: also, until I explicitly
> reply with that.
>
> > Signed-off-by: BingJing Chang <bingjingc@synology.com>
> > ---
> > include/linux/parser.h | 1 +
> > lib/parser.c | 44 +++++++++++++++++++++++++++++++++-----------
> > 2 files changed, 34 insertions(+), 11 deletions(-)
>
> The kernel-doc changes do look good. :)
>
> thanks.
> --
> ~Randy
>
Thanks,
BingJing
prev parent reply other threads:[~2021-01-29 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:13 [PATCH v2 1/3] parser: add unsigned int parser bingjingc
2021-01-28 21:24 ` Randy Dunlap
[not found] ` <6862f3e8-5eb6-4364-a05e-d4ad23d1d37d@Mail>
2021-01-29 6:07 ` bingjing chang [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=CAMmgxWEm-yLzxjFrnvjjtDMtim2FDrqxJQucgs40nBSW6Hj_1Q@mail.gmail.com \
--to=bxxxjxxg@gmail.com \
--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=rdunlap@infradead.org \
--cc=robbieko@synology.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@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).