From: Peter Hurley <peter@hurleysoftware.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Vinod Koul <vinod.koul@intel.com>, Felipe Balbi <balbi@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [4.0-rc+] WARNING: CPU: 0 PID: 1 at ./drivers/dma/dmaengine.c:863 dma_async_device_register+0xe0/0x540()
Date: Wed, 08 Apr 2015 12:07:14 -0400 [thread overview]
Message-ID: <55255232.40700@hurleysoftware.com> (raw)
In-Reply-To: <20150408155945.GG26727@lukather>
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.
Regards,
Peter Hurley
next prev parent reply other threads:[~2015-04-08 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:04 [4.0-rc+] WARNING: CPU: 0 PID: 1 at ./drivers/dma/dmaengine.c:863 dma_async_device_register+0xe0/0x540() Peter Hurley
2015-03-05 16:12 ` Vinod Koul
2015-04-08 15:53 ` Peter Hurley
2015-04-08 15:59 ` Maxime Ripard
2015-04-08 16:07 ` Peter Hurley [this message]
2015-04-08 16:09 ` Felipe Balbi
2015-04-08 16:23 ` Peter Hurley
2015-04-09 7:09 ` Maxime Ripard
2015-04-09 10:31 ` Peter Hurley
2015-04-09 11:49 ` Maxime Ripard
2015-04-08 16:26 ` Peter Hurley
2015-04-09 7:07 ` Maxime Ripard
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=55255232.40700@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=balbi@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=vinod.koul@intel.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).