From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: plagnioj@jcrosoft.com, tomi.valkeinen@ti.com
Cc: manuel.schoelling@gmx.de, jslaby@suse.cz,
gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, andrey_utkin@fastmail.com
Subject: [PATCH v4] console: Add persistent scrollback buffers for all VGA console
Date: Wed, 16 Nov 2016 17:38:51 +0000 [thread overview]
Message-ID: <1479317933-21849-1-git-send-email-manuel.schoelling@gmx.de> (raw)
In-Reply-To: <20161110214748.GB26324@dell-m4800.home>
---
Changes in v4:
- Rename from VGACON_SOFT_SCROLLBACK_FOR_EACH_CONSOLE to
VGACON_SOFT_SCROLLBACK_PERSISTENT
- Split into two patches
- Rework documentation
- Remove cosmetic changes in comments (postponed)
Changes in v3:
- Add config option for this feature
- Fallback to old scrollback buffer if kcalloc() fails
- Remove ioctl() call again and add documentation about existing
escape sequence to flush the scrollback buffer
Changes in v2:
- Add ioctl() call to flush scrollback buffer
- (Patch v2 was not labeled as such, sorry)
next prev parent reply other threads:[~2016-11-16 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 16:04 [PATCH v3] console: Add persistent scrollback buffers for all VGA consoles Manuel Schölling
2016-09-06 18:58 ` Manuel Schölling
2016-09-14 15:27 ` Manuel Schölling
2016-09-18 22:06 ` Manuel Schölling
2016-09-19 18:16 ` Manuel Schölling
2016-09-27 10:58 ` Greg KH
2016-11-10 21:47 ` Andrey Utkin
2016-11-16 17:38 ` Manuel Schölling [this message]
2016-11-16 20:30 ` [PATCH v4.1 0/2] console: Add persistent scrollback buffers for all VGA console Manuel Schölling
2016-11-16 20:30 ` [PATCH v4.1 1/2] console: Move scrollback data into its own struct Manuel Schölling
2016-11-16 20:31 ` [PATCH v4.1 2/2] console: Add persistent scrollback buffers for all VGA consoles Manuel Schölling
2016-11-16 21:40 ` kbuild test robot
2016-11-16 17:40 ` [PATCH v3] " Manuel Schölling
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=1479317933-21849-1-git-send-email-manuel.schoelling@gmx.de \
--to=manuel.schoelling@gmx.de \
--cc=andrey_utkin@fastmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
/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).