From: Linus Torvalds <torvalds@linux-foundation.org>
To: nick black <dankamongmen@gmail.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] console: consume APC, DM, DCS
Date: Mon, 30 Aug 2021 08:31:23 -0700 [thread overview]
Message-ID: <CAHk-=wg6-HbEPEC6-Fz0kqnHsB4nZryWi5TEZEN=NCWzBtg4iw@mail.gmail.com> (raw)
In-Reply-To: <YSysHCQyN+brJLEj@schwarzgerat.orthanc>
On Mon, Aug 30, 2021 at 2:59 AM nick black <dankamongmen@gmail.com> wrote:
>
> Jiri Slaby left as an exercise for the reader:
> > So simply:
> > return state == ESosc || state == ESapc || state == ESpm || state == ESdcs;
>
> Sure, I can do this. Would you like me to recut the patch?
>
> > I wonder if we can simply hide them all behind single ESignore?
>
> I'd rather not--I have plans beyond this patch which will
> require differentiating between them.
I've applied the patch as-is since I'm starting my merge window work
with "random patches in my queue".
I'm not 100% sure we care all that much about trying to make the
console be more vt100-compatible, considering how long we've been at
the current state.
But I have to admit to being slightly emotionally attached to us doing
reasonably well on this side. One of the original things Linux did was
console emulation, even before it was an OS..
Linus
next prev parent reply other threads:[~2021-08-30 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 8:56 [PATCH] console: consume APC, DM, DCS nick black
2021-08-30 9:17 ` Jiri Slaby
2021-08-30 9:59 ` nick black
2021-08-30 15:31 ` Linus Torvalds [this message]
2021-08-30 15:37 ` Linus Torvalds
2021-08-30 15:50 ` nick black
-- strict thread matches above, loose matches on Subject: below --
2021-08-19 3:48 nick black
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='CAHk-=wg6-HbEPEC6-Fz0kqnHsB4nZryWi5TEZEN=NCWzBtg4iw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dankamongmen@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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).