From: John Ogness <john.ogness@linutronix.de>
To: "John B. Wyatt IV" <jwyatt@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>,
Clark Williams <williams@redhat.com>,
Juri Lelli <jlelli@redhat.com>,
Derek Barbosa <debarbos@redhat.com>,
Bruno Goncalves <bgoncalv@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Automating console_blast.sh
Date: Mon, 19 Feb 2024 18:57:23 +0106 [thread overview]
Message-ID: <87frxo2vhg.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <ZdOQ2KzOIgYc8Ber@thinkpad2021>
On 2024-02-19, "John B. Wyatt IV" <jwyatt@redhat.com> wrote:
> I am investigating if we can automate, and, possibly add
> console_blash.sh [1] to our test suite here at Red Hat.
It is called "console_blast.sh". ;-)
> At Red Hat we use SSH to manage our test boxes. On an off-list email
> you wrote that 'Only the UART should be used as a console'. I took
> this as no ssh session should be used from the boot up until the
> crash, but I should have confirmed this. Is this correct?
SSH is fine. SSH sessions are not consoles. Consoles are specified with
the console= or netconsole= boot argument and receive the kernel
messages automatically from the kernel.
> The license for our test suite is GPL v3 [2]. May we have your
> permission to license it under that or permissive?
Yes, GPL v3 is OK.
> [1] https://lore.kernel.org/linux-rt-users/ZcQjxa4UA6hzXHnU@thinkpad2021/
>
> [2] https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/tree/main/rt-tests
John
next prev parent reply other threads:[~2024-02-19 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 17:33 Automating console_blast.sh John B. Wyatt IV
2024-02-19 17:51 ` John Ogness [this message]
2024-02-20 22:26 ` John B. Wyatt IV
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=87frxo2vhg.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=bgoncalv@redhat.com \
--cc=debarbos@redhat.com \
--cc=jlelli@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sageofredondo@gmail.com \
--cc=williams@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