From: Storm Dragon <stormdragon2976@gmail.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: George Kennedy <george.kennedy@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] vc_screen: don't clobber return value in vcs_read
Date: Fri, 3 Mar 2023 16:46:21 -0500 [thread overview]
Message-ID: <ZAJqrfcfoM2eO5VL@mjollnir> (raw)
In-Reply-To: <00e5aee7-c7b3-4077-8c9f-4f28ec220567@t-8ch.de>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Fri, Mar 03, 2023 at 09:12:50PM +0000, Thomas Weißschuh wrote:
>Sorry for the long delay, but this should be fixed in the current round
>of stable kernels. Can you try the following:
>
>pacman -U https://mirrors.edge.kernel.org/archlinux/testing/os/x86_64/linux-6.2.2.arch1-1-x86_64.pkg.tar.zst
>
>Thomas
I have installed the package above. My screen reader is behaving much
better now. Interestingly, however, trying to cat the /dev/vcs device
still shows the following:
cat: /dev/vcs: No such device or address
cat: /dev/vcsa: No such device or address
cat: /dev/vcsa1: No such device or address
Is this expected behavior?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-03 21:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 21:21 Bug with /dev/vcs* devices Storm Dragon
2023-02-19 22:11 ` Randy Dunlap
2023-02-19 23:13 ` Storm Dragon
2023-02-20 6:46 ` [PATCH] vc_screen: don't clobber return value in vcs_read linux
2023-02-20 11:48 ` Jiri Slaby
2023-02-20 16:34 ` Thomas Weißschuh
2023-02-21 13:30 ` George Kennedy
2023-02-21 13:49 ` Thomas Weißschuh
2023-02-21 13:50 ` Greg Kroah-Hartman
2023-02-27 14:20 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-27 19:59 ` George Kennedy
2023-02-28 5:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-20 16:06 ` Storm Dragon
2023-03-03 21:12 ` Thomas Weißschuh
2023-03-03 21:46 ` Storm Dragon [this message]
2023-03-03 23:25 ` Thomas Weißschuh
2023-03-04 3:30 ` Storm Dragon
2023-03-04 3:42 ` Storm Dragon
2023-03-04 19:58 ` Storm Dragon
2023-03-04 22:33 ` Thomas Weißschuh
2023-03-10 21:32 ` Thomas Weißschuh
2023-02-24 14:25 ` Bug with /dev/vcs* devices Thomas Weißschuh
2023-02-28 4:29 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZAJqrfcfoM2eO5VL@mjollnir \
--to=stormdragon2976@gmail.com \
--cc=george.kennedy@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.