All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <benh@debian.org>
To: Steve McIntyre <93sam@debian.org>, kernelci@groups.io
Subject: Re: Testing Debian kernels on kernelci?
Date: Mon, 18 Feb 2019 18:09:27 +0000	[thread overview]
Message-ID: <ac7530daba2a2a42c7a1d254409cbbe34d9a2648.camel@debian.org> (raw)
In-Reply-To: <20190218165402.obkznz2itzlqeys7@tack.einval.com>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Mon, 2019-02-18 at 16:54 +0000, Steve McIntyre wrote:
> [ CC: to Ben, the debian kernel team lead ]
> 
> Hi folks,
> 
> In Debian we've just been bitten by quite a nasty kernel bug in our
> latest stable release [1], and this has clearly managed to make it
> into a release due to a insufficient testing of our kernels on all our
> platforms. Most people only have x86 hardware, and doing full
> regression testing across multiple Arm, MIPS, etc. platforms is beyond
> our capabilities. You know, the usual situation... :-)
> 
> Due to my position in the LAVA team in Linaro, I know quite a bit
> about kernelci and I'm wondering if it would be possible to get some
> of our Debian kernel branches added to the list for at least some
> automated boot testing. This would be major help for us.

The last time I looked, KernelCI assumed all essential drivers would be
built in and only supported use of a pre-built initramfs (if any).

Debian kernel packages are modularised almost as far as possible, so
for each kernel build the initramfs will also need to be rebuilt to
include the new kernel modules.

Ben.

> [1]  https://bugs.debian.org/922478
> 
-- 
Ben Hutchings - Debian developer, member of kernel, installer and LTS teams

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-02-18 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 16:54 Testing Debian kernels on kernelci? Steve McIntyre
2019-02-18 18:09 ` Ben Hutchings [this message]
2019-02-18 18:54   ` Mark Brown

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=ac7530daba2a2a42c7a1d254409cbbe34d9a2648.camel@debian.org \
    --to=benh@debian.org \
    --cc=93sam@debian.org \
    --cc=kernelci@groups.io \
    /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.