From: Greg KH <gregkh@linuxfoundation.org>
To: "zhangjianhua (E)" <chris.zjh@huawei.com>
Cc: jirislaby@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] vt: defkeymap.c_shipped remove unused variables
Date: Thu, 5 May 2022 14:23:12 +0200 [thread overview]
Message-ID: <YnPBsEiaUfbEI+Ef@kroah.com> (raw)
In-Reply-To: <53e36000-ad70-9de7-74ad-16bd81dae530@huawei.com>
On Thu, May 05, 2022 at 11:10:55AM +0800, zhangjianhua (E) wrote:
>
> 在 2022/4/29 14:39, Greg KH 写道:
> > On Fri, Apr 29, 2022 at 09:48:14AM +0800, Zhang Jianhua wrote:
> > > The global variables 'funcbufptr' 'funcbufsize' and 'funcbufleft' have
> > > been initialized but not used, they are redundant and remove them.
> > >
> > > --------
> > Why this extra "------" line?
>
> This line "------" means the end of commit message, if it is redundant, I will remove it in next version.
That is not used in kernel changelogs at all, sorry. Please don't add
it in future changes either.
thanks,
greg k-h
prev parent reply other threads:[~2022-05-05 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 1:48 [PATCH -next] vt: defkeymap.c_shipped remove unused variables Zhang Jianhua
2022-04-29 6:39 ` Greg KH
2022-05-05 3:10 ` zhangjianhua (E)
2022-05-05 12:23 ` Greg KH [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=YnPBsEiaUfbEI+Ef@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris.zjh@huawei.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.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