From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [Bug]: mtd: onenand: omap2plus: kernel panic with OneNAND on OMAP3 (DM3730) device GTA04A5 Date: Thu, 12 Apr 2018 08:03:06 -0700 Message-ID: <20180412150306.GB5700@atomide.com> References: <5D496D5C-4E3E-47B4-9981-E8F4C348DE00@goldelico.com> <20180410205643.GA2228@lenoch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "H. Nikolaus Schaller" Cc: Ladislav Michl , Boris Brezillon , Peter Ujfalusi , Aaro Koskinen , Roger Quadros , Linux Kernel Mailing List , linux-omap , Discussions about the Letux Kernel List-Id: linux-omap@vger.kernel.org * H. Nikolaus Schaller [180411 07:05]: > > Am 10.04.2018 um 22:56 schrieb Ladislav Michl : > > 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