public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@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 11:02:57 +0200	[thread overview]
Message-ID: <20241014090257.12624-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20241014-s390-kunit-v1-0-941defa765a6@linutronix.de>

On Mon, Oct 14, 2024 at 07:50:05AM +0200, Thomas Weißschuh wrote:
> 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(-)

Applied, thanks!

      parent reply	other threads:[~2024-10-14  9:03 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 ` [PATCH 0/2] s390: two bugfixes (for kunit) Sven Schnelle
2024-10-14  9:02 ` Heiko Carstens [this message]

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=20241014090257.12624-A-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=gpiccoli@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --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