[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150408160955.GD1738@saruman.tx.rr.com>
Date: Wed, 8 Apr 2015 11:09:55 -0500
From: Felipe Balbi <balbi@...com>
To: Peter Hurley <peter@...leysoftware.com>
CC: Maxime Ripard <maxime.ripard@...e-electrons.com>,
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, and
> this was at least known since Mar 5 (and likely earlier); arguing that
> it's late in the cycle is a bit disingenuous.
In Vinod's defense, he asked for changes in my patch which I didn't have
time to implement (as of yet). Have been rather busy lately with a bunch
of other things, I'll try to get to those changes ASAP, just need to
finish up a bisect on another platform.
cheers
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists