From: Sven Schnelle <svens@linux.ibm.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 0/2] s390: two bugfixes (for kunit)
Date: Mon, 14 Oct 2024 10:54:28 +0200 [thread overview]
Message-ID: <yt9dmsj712uz.fsf@linux.ibm.com> (raw)
In-Reply-To: <20241014-s390-kunit-v1-0-941defa765a6@linutronix.de> ("Thomas Weißschuh"'s message of "Mon, 14 Oct 2024 07:50:05 +0200")
Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> When trying to use kunit for s390 with
> ./tools/testing/kunit/kunit.py run --arch=s390 --kunitconfig drivers/base/test --cross_compile=$CROSS_COMPILE
> I ran into some bugs.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> Thomas Weißschuh (2):
> s390/sclp: deactivate sclp after all its users
> s390/sclp_vt220: convert newlines to CRLF instead of LFCR
>
> drivers/s390/char/sclp.c | 3 ++-
> drivers/s390/char/sclp_vt220.c | 4 ++--
> 2 files changed, 4 insertions(+), 3 deletions(-)
> ---
> base-commit: 6485cf5ea253d40d507cd71253c9568c5470cd27
> change-id: 20241014-s390-kunit-47cbc26a99e6
Looks good to me. For both patches:
Reviewed-by: Sven Schnelle <svens@linux.ibm.com>
Thanks!
Sven
next prev parent reply other threads:[~2024-10-14 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 5:50 [PATCH 0/2] s390: two bugfixes (for kunit) Thomas Weißschuh
2024-10-14 5:50 ` [PATCH 1/2] s390/sclp: deactivate sclp after all its users Thomas Weißschuh
2024-10-14 5:50 ` [PATCH 2/2] s390/sclp_vt220: convert newlines to CRLF instead of LFCR Thomas Weißschuh
2024-10-14 8:54 ` Sven Schnelle [this message]
2024-10-14 9:02 ` [PATCH 0/2] s390: two bugfixes (for kunit) Heiko Carstens
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=yt9dmsj712uz.fsf@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=gpiccoli@igalia.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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