From: Jiri Slaby <jirislaby@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] tty/vt: Makefile, add --unicode for loadkeys invocation
Date: Tue, 7 Jun 2022 07:42:20 +0200 [thread overview]
Message-ID: <4d4549ef-f8f8-d0cb-6d27-e6200aa14048@kernel.org> (raw)
In-Reply-To: <CAHp75VfsR6sVwO9iF6RA0bhVjMF1jC1_JEkv106TubPgL_m8YA@mail.gmail.com>
On 06. 06. 22, 16:35, Andy Shevchenko wrote:
> On Thu, Jun 2, 2022 at 12:30 PM Jiri Slaby <jslaby@suse.cz> wrote:
>>
>> For a long time, we generate unicode tables using loadkeys. So fix
>> Makefile to use that flag too.
>
> generated
We still do, but I didn't even know there is even a rule for that ;).
> Does it make sense to add the Fixes tag?
I don't think so -- I don't think anyone ran the rule in the past decade
:P. I.e. it'd be pre-git anyway.
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
>
>> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
>> ---
>> drivers/tty/vt/Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/tty/vt/Makefile b/drivers/tty/vt/Makefile
>> index fe30ce512819..b3dfe9d5717e 100644
>> --- a/drivers/tty/vt/Makefile
>> +++ b/drivers/tty/vt/Makefile
>> @@ -30,6 +30,6 @@ $(obj)/defkeymap.o: $(obj)/defkeymap.c
>> ifdef GENERATE_KEYMAP
>>
>> $(obj)/defkeymap.c: $(obj)/%.c: $(src)/%.map
>> - loadkeys --mktable $< > $@
>> + loadkeys --mktable --unicode $< > $@
>>
>> endif
>> --
>> 2.36.1
>>
>
>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2022-06-07 5:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 8:31 [PATCH 1/2] tty/vt: defkeymap.c_shipped, little unification with loadkeys Jiri Slaby
2022-06-02 8:31 ` [PATCH 2/2] tty/vt: Makefile, add --unicode for loadkeys invocation Jiri Slaby
2022-06-06 14:35 ` Andy Shevchenko
2022-06-07 5:42 ` Jiri Slaby [this message]
2022-06-07 9:58 ` Andy Shevchenko
2022-06-07 10:01 ` Andy Shevchenko
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=4d4549ef-f8f8-d0cb-6d27-e6200aa14048@kernel.org \
--to=jirislaby@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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®