From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Ladislav Michl <ladis@linux-mips.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Roger Quadros <rogerq@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
Discussions about the Letux Kernel <letux-kernel@openphoenux.org>
Subject: Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5
Date: Thu, 12 Apr 2018 08:03:06 -0700 [thread overview]
Message-ID: <20180412150306.GB5700@atomide.com> (raw)
In-Reply-To: <AF1CE94F-FE95-49B1-99FF-AEC0C3EFFCA1@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [180411 07:05]:
> > Am 10.04.2018 um 22:56 schrieb Ladislav Michl <ladis@linux-mips.org>:
> > Well, that's a shame... However, this code is in production for several
> > months now,
>
> Well, we could have tested earlier release-candidates...
I've found it's way easier to test Linux next on regular basis
and report the regressions compared to chasing regressions after
the merge window or tagged kernels. By that time you may have
already multiple regressions to deal with which is always fun.
If you have products running with mainline kernel, maybe set up
automated boot testing for core devices to catch regressions
early?
Regards,
Tony
next prev parent reply other threads:[~2018-04-12 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 16:25 [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5 H. Nikolaus Schaller
2018-04-10 20:56 ` Ladislav Michl
2018-04-11 4:59 ` [Letux-kernel] " Andreas Kemnade
2018-04-11 6:26 ` Ladislav Michl
2018-04-11 7:15 ` Boris Brezillon
2018-04-11 7:36 ` Ladislav Michl
2018-04-11 8:08 ` Boris Brezillon
2018-04-11 8:27 ` Ladislav Michl
2018-04-11 8:52 ` Boris Brezillon
2018-04-11 9:12 ` Ladislav Michl
2018-04-11 9:44 ` H. Nikolaus Schaller
2018-04-12 16:27 ` Boris Brezillon
2018-04-11 7:03 ` H. Nikolaus Schaller
2018-04-12 15:03 ` Tony Lindgren [this message]
2018-04-12 15:51 ` H. Nikolaus Schaller
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=20180412150306.GB5700@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=boris.brezillon@free-electrons.com \
--cc=hns@goldelico.com \
--cc=ladis@linux-mips.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=rogerq@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