From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
kernelci-results@groups.io,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
Richard Weinberger <richard@nod.at>,
Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd@lists.infradead.org
Subject: Re: next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3N
Date: Thu, 18 Jun 2020 16:36:02 +0200 [thread overview]
Message-ID: <20200618163602.1727fffd@xps13> (raw)
In-Reply-To: <0c00fe0b-c38b-3d69-8f93-3fe8c3675113@collabora.com>
Hi Guillaume,
-reducing the Cc: list
Guillaume Tucker <guillaume.tucker@collabora.com> wrote on Thu, 18 Jun
2020 15:23:45 +0100:
> On 18/06/2020 15:09, Miquel Raynal wrote:
> > Hi Guillaume,
> >
> > Miquel Raynal <miquel.raynal@bootlin.com> wrote on Thu, 18 Jun 2020
> > 15:23:24 +0200:
> >
> >> Hi Guillaume,
> >>
> >> Guillaume Tucker <guillaume.tucker@collabora.com> wrote on Thu, 18 Jun
> >> 2020 13:28:05 +0100:
> >>
> >>> Please see the bisection report below about a kernel panic.
> >>>
> >>> Reports aren't automatically sent to the public while we're
> >>> trialing new bisection features on kernelci.org but this one
> >>> looks valid.
> >>>
> >>> See the kernel Oops due to a NULL pointer followed by a panic:
> >>>
> >>> https://storage.kernelci.org/next/master/next-20200618/arm/oxnas_v6_defconfig/gcc-8/lab-baylibre/baseline-ox820-cloudengines-pogoplug-series-3.html#L504
> >>
> >> Thanks for the report, I will not be able to manage it before Monday,
> >> but I'll try to take care of it early next week.
> >
> > Actually Boris saw the issue, I just updated nand/next, it should be
> > part of tomorrow's linux-next. Could you please report if it fixes your
> > boot?
>
> Sure, will check tomorrow. Thanks for the update.
>
> We may also consider adding the nand/next branch to kernelci.org
> and catch issues earlier. We can discuss that separately.
That would be great! So far, we -MTD- have been lazy and relied on
linux-next testing only. We do code analysis with Intel's 0-day robots
but they tend to be very slow when approaching -rc6/-rc7 which is also
an issue for us because of the wide variety of architectures we still
support.
Currently we maintain the following branches, which are all pulled
in linux-next:
* nand/next -> Raw NAND and SPI-NAND stuff
* spi-nor/next -> SPI-NOR stuff
* cfi/next -> CFI stuff
* mtd/next -> everything else
* mtd/fixes occasionally for all MTD fixes (no subsystem specific
branch)
Are there any kernel-ci prerequisites we should be aware of?
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-06-18 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5eeb5bf7.1c69fb81.4f6e3.8979@mx.google.com>
2020-06-18 12:28 ` next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3 Guillaume Tucker
2020-06-18 13:23 ` Miquel Raynal
2020-06-18 14:09 ` Miquel Raynal
2020-06-18 14:23 ` Guillaume Tucker
2020-06-18 14:33 ` Boris Brezillon
2020-06-18 14:36 ` Miquel Raynal [this message]
2020-06-18 14:59 ` next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3N Guillaume Tucker
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=20200618163602.1727fffd@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=boris.brezillon@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).