From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 5.14
Date: Mon, 30 Aug 2021 10:11:30 +0100 [thread overview]
Message-ID: <CADVatmP8HQfZBPevLuuWtWh=1eBD=cmY84iJoMcoHh0n480Bag@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wh75ELUu99yPkPNt+R166CK=-M4eoV+F62tW3TVgB7=4g@mail.gmail.com>
Hi All,
On Sun, Aug 29, 2021 at 11:23 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
<snip>
>
> Of course, the poor tireless kernel maintainers won't have time for
> the festivities, because for them, this just means that the merge
> window will start tomorrow. We have another 30 years to look forward
> to, after all. But for the rest of you, take a breather, build a
> kernel, test it out, and then you can go back to the seemingly endless
> party that I'm sure you just crawled out of.
We were recently working on openqa based testing and is a very basic
testing for now.. Build the kernel for x86_64 and arm64, boot it on
qemu and rpi4 and test that the desktop environment is working. And,
it now tests mainline branch every night. So, last night it tested
"5.14.0-7d2a07b76933" and both tests were ok.
rpi4: https://openqa.qa.codethink.co.uk/tests/68
qemu: https://openqa.qa.codethink.co.uk/tests/67
--
Regards
Sudip
next prev parent reply other threads:[~2021-08-30 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 22:19 Linux 5.14 Linus Torvalds
2021-08-30 9:11 ` Sudip Mukherjee [this message]
2021-08-30 15:17 ` Linus Torvalds
2021-09-12 19:29 ` Sudip Mukherjee
2021-08-30 9:39 ` Andy Shevchenko
2021-08-30 11:28 ` Andy Shevchenko
2021-08-30 20:12 ` Guenter Roeck
2021-08-30 20:15 ` Linus Torvalds
2021-08-30 21:28 ` Peter Zijlstra
2021-08-31 11:04 ` Heiko Carstens
2021-08-30 20:32 ` Thomas Gleixner
2021-08-30 23:57 ` Thomas Gleixner
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='CADVatmP8HQfZBPevLuuWtWh=1eBD=cmY84iJoMcoHh0n480Bag@mail.gmail.com' \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).