From: Jan Kara <jack@suse.cz>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: bingjingc <bingjingc@synology.com>,
kuba@kernel.org, linux-kernel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH] parser: Fix kernel-doc markups
Date: Wed, 3 Feb 2021 19:12:13 +0100 [thread overview]
Message-ID: <20210203181213.GB20183@quack2.suse.cz> (raw)
In-Reply-To: <f5cd0b56-de00-bc4f-d4c6-9108d7cab780@infradead.org>
On Thu 28-01-21 22:39:46, Randy Dunlap wrote:
> On 1/28/21 9:00 PM, bingjingc wrote:
> > From: BingJing Chang <bingjingc@synology.com>
> >
> > Fix existing issues at the kernel-doc markups
> >
> > Signed-off-by: BingJing Chang <bingjingc@synology.com>
> > ---
> > lib/parser.c | 22 +++++++++++-----------
> > 1 file changed, 11 insertions(+), 11 deletions(-)
> >
>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>
> thanks for the kernel-doc patch.
Thanks for the patch and review. Since this is somewhat related to the
match_uint() fixes, I've just picked up this patch to my tree as well since
I don't think we have a designated lib/parser.c maintainer...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2021-02-03 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 5:00 [PATCH] parser: Fix kernel-doc markups bingjingc
2021-01-29 6:39 ` Randy Dunlap
2021-02-03 18:12 ` Jan Kara [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=20210203181213.GB20183@quack2.suse.cz \
--to=jack@suse.cz \
--cc=bingjingc@synology.com \
--cc=kuba@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).