From: Dominique Martinet <asmadeus@codewreck.org>
To: zhengbin <zhengbin13@huawei.com>
Cc: ericvh@gmail.com, lucho@ionkov.net,
v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] 9p: Remove unneeded semicolon
Date: Thu, 19 Dec 2019 12:34:06 +0100 [thread overview]
Message-ID: <20191219113406.GA22811@nautica> (raw)
In-Reply-To: <1576752517-58292-1-git-send-email-zhengbin13@huawei.com>
zhengbin wrote on Thu, Dec 19, 2019:
> Fixes coccicheck warning:
>
> fs/9p/vfs_inode.c:146:3-4: Unneeded semicolon
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: zhengbin <zhengbin13@huawei.com>
Taken, will be in linux-next in the next few days.
Please note I won't submit a pull request to Linus if I only have this
so it might take an extra couple of months to get in depending on what
patches get sent.
--
Dominique
prev parent reply other threads:[~2019-12-19 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 10:48 [PATCH RESEND] 9p: Remove unneeded semicolon zhengbin
2019-12-19 11:34 ` Dominique Martinet [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=20191219113406.GA22811@nautica \
--to=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=zhengbin13@huawei.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