From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH 1/2] automation: build 6.1.19 kernel for x86-64 dom0
Date: Sat, 25 Mar 2023 16:55:30 +0100 [thread overview]
Message-ID: <ZB8Zcwhj+eszsHfu@mail-itl> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2303171436360.3359@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Fri, Mar 17, 2023 at 03:01:14PM -0700, Stefano Stabellini wrote:
> On Fri, 17 Mar 2023, Marek Marczykowski-Górecki wrote:
> > It will be used in tests added in subsequent patches.
> > Enable config options needed for those tests.
>
> Thanks for the patch! Looks great.
>
> Can you also remove the old 5.10.74 Dockerfile
> (automation/tests-artifacts/kernel/5.10.74.dockerfile), the
> kernel-5.10.74-export job as well and replace kernel-5.10.74-export with
> kernel-6.1.19-export as dependency for the qemu-alpine-x86_64-gcc test
> job?
>
> I think it makes sense to just keep kernel-6.1.19-export. I tested the
> below already and it works fine.
I'll adjust this patch as suggested, but generally, I think it's worth
keeping some tests on older kernel to detect regressions (for example in
API not used anymore by newer kernels). That said, it's probably more
beneficial to "simply" test specific older (but still supported)
distribution [kernel], not a custom build of an older version. And
adding that would be a separate patch.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-25 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 3:34 [PATCH 0/2] automation: add another Gitlab-CI test, x86-64 S3 this time Marek Marczykowski-Górecki
2023-03-17 3:34 ` [PATCH 1/2] automation: build 6.1.19 kernel for x86-64 dom0 Marek Marczykowski-Górecki
2023-03-17 22:01 ` Stefano Stabellini
2023-03-25 15:55 ` Marek Marczykowski-Górecki [this message]
2023-03-17 3:34 ` [PATCH 2/2] automation: add a suspend test on an Alder Lake system Marek Marczykowski-Górecki
2023-03-17 23:10 ` Stefano Stabellini
2023-03-18 0:53 ` Marek Marczykowski-Górecki
2023-03-20 20:08 ` Stefano Stabellini
2023-03-20 20:36 ` Marek Marczykowski-Górecki
2023-03-20 20:41 ` Stefano Stabellini
2023-03-20 20:55 ` Marek Marczykowski-Górecki
2023-03-20 21:40 ` Stefano Stabellini
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=ZB8Zcwhj+eszsHfu@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=cardoe@cardoe.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.