mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "zhangjianhua (E)" <chris.zjh@huawei.com>
To: Jiri Slaby <jirislaby@kernel.org>, <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next v2] vt: defkeymap.c_shipped remove unused variables
Date: Mon, 16 May 2022 22:26:29 +0800	[thread overview]
Message-ID: <147d2f77-43db-40b7-aa36-a06d558f1813@huawei.com> (raw)
In-Reply-To: <49a7602f-dd79-cac3-e6e0-83c4c41fcd53@kernel.org>


在 2022/5/16 15:00, Jiri Slaby 写道:
> On 13. 05. 22, 3:54, Zhang Jianhua wrote:
>> The global variables 'funcbufptr' 'funcbufsize' and 'funcbufleft' have
>> been initialized but not used, they are redundant and remove them.
>>
>> Signed-off-by: Zhang Jianhua <chris.zjh@huawei.com>
>>
>> ---
>> No code changes since v1, only remove the redundant line "--------" in
>> v1 commit message.
>> ---
>>   drivers/tty/vt/defkeymap.c_shipped | 4 ----
>
> The file header says:
> /* Do not edit this file! It was automatically generated by   */
> /*    loadkeys --mktable defkeymap.map > defkeymap.c */
>
> So I'm not sure anyone wants to touch it.
This notes will be copied to the file defkeymap.c completely which is 
automatically generated, so it says to defkeymap.c rather than defkeymap.map
>
>> --- a/drivers/tty/vt/defkeymap.c_shipped
>> +++ b/drivers/tty/vt/defkeymap.c_shipped
>> @@ -185,10 +185,6 @@ char func_buf[] = {
>>       '\033', '[', 'P', 0,
>>   };
>>   -char *funcbufptr = func_buf;
>> -int funcbufsize = sizeof(func_buf);
>> -int funcbufleft = 0;          /* space left */
>> -
>>   char *func_table[MAX_NR_FUNC] = {
>>       func_buf + 0,
>>       func_buf + 5,
>
>

      reply	other threads:[~2022-05-16 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  1:54 Zhang Jianhua
2022-05-16  7:00 ` Jiri Slaby
2022-05-16 14:26   ` zhangjianhua (E) [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=147d2f77-43db-40b7-aa36-a06d558f1813@huawei.com \
    --to=chris.zjh@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®