From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Adam Borowski <kilobyte@angband.pl>, Dave Mielke <Dave@mielke.cc>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-console@vger.kernel.org
Subject: Re: [PATCH 3/3] vt: add /dev/vcsu* to devices.txt
Date: Wed, 18 Jul 2018 09:25:14 +0200 [thread overview]
Message-ID: <CAMuHMdUB4DvxGv6ogcm9UiV-4BHZHWKyGwSPsGELMru7D9dHaQ@mail.gmail.com> (raw)
In-Reply-To: <20180718010242.5254-4-nicolas.pitre@linaro.org>
On Wed, Jul 18, 2018 at 3:02 AM Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> Also mention that the traditional devices provide glyph values whereas
> /dev/vcsu* is unicode based.
>
> Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Nicolas Pitre <nico@linaro.org>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-07-18 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 1:02 [PATCH 0/3] follow-up to the unicode vt console series Nicolas Pitre
2018-07-18 1:02 ` [PATCH 1/3] vt: avoid a VLA in the unicode screen scroll function Nicolas Pitre
2018-07-18 1:48 ` Adam Borowski
2018-07-18 2:54 ` Nicolas Pitre
2018-07-19 4:05 ` Nicolas Pitre
2018-07-21 7:20 ` [PATCH v2 " Greg Kroah-Hartman
2018-07-18 1:02 ` [PATCH 2/3] vt: coherence validation code for the unicode screen buffer Nicolas Pitre
2018-07-18 1:02 ` [PATCH 3/3] vt: add /dev/vcsu* to devices.txt Nicolas Pitre
2018-07-18 7:25 ` Geert Uytterhoeven [this message]
2018-07-18 14:04 ` [PATCH 0/3] follow-up to the unicode vt console series Kees Cook
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=CAMuHMdUB4DvxGv6ogcm9UiV-4BHZHWKyGwSPsGELMru7D9dHaQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Dave@mielke.cc \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kilobyte@angband.pl \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=samuel.thibault@ens-lyon.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).