public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Storm Dragon <stormdragon2976@gmail.com>
To: 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: Mon, 20 Feb 2023 11:06:08 -0500	[thread overview]
Message-ID: <Y/OacHw6nL/ZtrH3@hotmail.com> (raw)
In-Reply-To: <20230220064612.1783-1-linux@weissschuh.net>

[-- Attachment #1: Type: text/plain, Size: 368 bytes --]

On Mon, Feb 20, 2023 at 06:46:12AM +0000, linux@weissschuh.net wrote:
>From: Thomas Weißschuh <linux@weissschuh.net>
>
>@Storm Could you validate this patch?


I am willing to test, but I have almost no experience doing anything
with the kernel other than upgrading it from time to time. Can you send
me some instructions for testing this?

Thanks,
Storm

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-02-20 16:06 UTC|newest]

Thread overview: 21+ 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 [this message]
2023-03-03 21:12         ` Thomas Weißschuh
2023-03-03 21:46           ` Storm Dragon
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

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=Y/OacHw6nL/ZtrH3@hotmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox