[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150409070927.GI26727@lukather>
Date: Thu, 9 Apr 2015 09:09:27 +0200
From: Maxime Ripard <maxime.ripard@...e-electrons.com>
To: Peter Hurley <peter@...leysoftware.com>
Cc: Vinod Koul <vinod.koul@...el.com>, Felipe Balbi <balbi@...com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [4.0-rc+] WARNING: CPU: 0 PID: 1 at
./drivers/dma/dmaengine.c:863 dma_async_device_register+0xe0/0x540()
On Wed, Apr 08, 2015 at 12:07:14PM -0400, Peter Hurley wrote:
> On 04/08/2015 11:59 AM, Maxime Ripard wrote:
> > On Wed, Apr 08, 2015 at 11:53:33AM -0400, Peter Hurley wrote:
> >> On 03/05/2015 11:12 AM, Vinod Koul wrote:
> >>> On Thu, Mar 05, 2015 at 10:04:21AM -0500, Peter Hurley wrote:
> >>>>> First boot of 4.0-rc+ gave me [1] on a Beaglebone Black due to
> >>>>>
> >>> The warning is intentional to get driver fixed and give the right behaviour
> >>>
> >>> Felipe had sent a patch for this but that one needs an update
> >>
> >> Vinod,
> >>
> >> Felipe's patch never made it to mainline, and this warning is
> >> still happening on 4.0-rc7 so please revert for 4.0-final.
> >
> > That patch isn't introducing any regression. I fail to see how that
> > justifies a revert so late in the release cycle.
>
> Arguably it never should have been introduced in the first place
Upon which arguments? So far, I've seen none but "my boot logs look
bad now".
> and this was at least known since Mar 5 (and likely earlier);
> arguing that it's late in the cycle is a bit disingenuous.
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists