From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, thuth@redhat.com, david@redhat.com,
nsg@linux.ibm.com, nrb@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 3/3] lib: s390x: sclp: Add line mode input handling
Date: Tue, 10 Oct 2023 13:05:59 +0200 [thread overview]
Message-ID: <8568bef1-e829-40f3-8815-c5ab1e9dc8ef@linux.ibm.com> (raw)
In-Reply-To: <20231010123309.4dd54963@p-imbrenda>
On 10/10/23 12:33, Claudio Imbrenda wrote:
> On Tue, 10 Oct 2023 07:38:55 +0000
> Janosch Frank <frankja@linux.ibm.com> wrote:
>
>> Time to add line-mode input so we can use input handling under LPAR if
>> there's no access to a ASCII console.
>>
>> Line-mode IO is pretty wild and the documentation could be improved a
>> lot. Hence I've copied the input parsing functions from Linux.
>>
>> For some reason output is a type 2 event but input is a type 1
>> event. This also means that the input and output structures are
>> different from each other.
>>
>> The input can consist of multiple structures which don't contain text
>> data before the input text data is reached. Hence we need a bunch of
>> search functions to retrieve a pointer to the text data.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> lib/s390x/sclp-console.c | 180 ++++++++++++++++++++++++++++++++++-----
>> lib/s390x/sclp.h | 26 +++++-
>> 2 files changed, 185 insertions(+), 21 deletions(-)
>>
>> diff --git a/lib/s390x/sclp-console.c b/lib/s390x/sclp-console.c
>> index 313be1e4..23c09b70 100644
>> --- a/lib/s390x/sclp-console.c
>> +++ b/lib/s390x/sclp-console.c
>> @@ -1,8 +1,12 @@
>> /* SPDX-License-Identifier: GPL-2.0-or-later */
>> /*
>> - * SCLP ASCII access driver
>> + * SCLP line mode and ASCII console driver
>> *
>> * Copyright (c) 2013 Alexander Graf <agraf@suse.de>
>> + *
>> + * Copyright IBM Corp. 1999
>> + * Author(s): Martin Peschke <mpeschke@de.ibm.com>
>> + * Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> from the weird copyright notices that you are adding I deduce that you
> copied those functions from the kernel. maybe add a line in the patch
> description to say so? or at least explain better in the comment itself.
You mean this line which is in the patch description?
"Hence I've copied the input parsing functions from Linux."
But sure, I could add that after "SCLP line mode and ASCII console driver"
next prev parent reply other threads:[~2023-10-10 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 7:38 [kvm-unit-tests PATCH 0/3] s390x: Improve console handling Janosch Frank
2023-10-10 7:38 ` [kvm-unit-tests PATCH 1/3] lib: s390x: hw: Provide early detect host Janosch Frank
2023-10-10 10:40 ` Claudio Imbrenda
2023-10-10 11:03 ` Janosch Frank
2023-10-10 11:42 ` Claudio Imbrenda
2023-10-12 11:13 ` Janosch Frank
2023-10-10 7:38 ` [kvm-unit-tests PATCH 2/3] lib: s390x: sclp: Add compat handling for HMC ASCII consoles Janosch Frank
2023-10-10 8:35 ` Nico Boehr
2023-10-10 8:57 ` Janosch Frank
2023-10-10 12:35 ` Nico Boehr
2023-10-10 7:38 ` [kvm-unit-tests PATCH 3/3] lib: s390x: sclp: Add line mode input handling Janosch Frank
2023-10-10 10:33 ` Claudio Imbrenda
2023-10-10 11:05 ` Janosch Frank [this message]
2023-10-10 11:44 ` Claudio Imbrenda
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=8568bef1-e829-40f3-8815-c5ab1e9dc8ef@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=thuth@redhat.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