From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
"Rich Felker" <dalias@libc.org>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Willy Tarreau" <w@1wt.eu>, "Shuah Khan" <shuah@kernel.org>
Cc: <linux-sh@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] selftests/nolibc: use file driver for QEMU serial
Date: Tue, 24 Jun 2025 11:56:14 +0300 [thread overview]
Message-ID: <af7b93bf-6f9c-4d4b-85fd-ccf93769d346@omp.ru> (raw)
In-Reply-To: <20250623-nolibc-sh-v2-2-0f5b4b303025@weissschuh.net>
On 6/24/25 12:15 AM, Thomas Weißschuh wrote:
> For the test implementation of the SuperH architecture a second serial
> serial port needs to be used. Unfortunately the currently used 'stdio'
"Serial" typed twice? :-)
> driver does not support multiple serial ports at the same time.
>
> Switch to the 'file' driver which does support multiple ports and is
> sufficient for the nolibc-test usecase.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> Acked-by: Willy Tarreau <w@1wt.eu>
[...]
MBR, Sergey
next prev parent reply other threads:[~2025-06-24 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 21:15 [PATCH v2 0/3] tools/nolibc: add support for SuperH Thomas Weißschuh
2025-06-23 21:15 ` [PATCH v2 1/3] selftests/nolibc: fix EXTRACONFIG variables ordering Thomas Weißschuh
2025-06-23 21:15 ` [PATCH v2 2/3] selftests/nolibc: use file driver for QEMU serial Thomas Weißschuh
2025-06-24 8:56 ` Sergey Shtylyov [this message]
2025-06-23 21:15 ` [PATCH v2 3/3] tools/nolibc: add support for SuperH Thomas Weißschuh
2025-06-24 6:03 ` [PATCH v2 0/3] " John Paul Adrian Glaubitz
2025-06-24 6:07 ` Willy Tarreau
2025-06-25 9:47 ` John Paul Adrian Glaubitz
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=af7b93bf-6f9c-4d4b-85fd-ccf93769d346@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
--cc=ysato@users.sourceforge.jp \
/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