linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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: Thu, 9 Apr 2015 09:07:12 +0200	[thread overview]
Message-ID: <20150409070712.GH26727@lukather> (raw)
In-Reply-To: <552556A5.5070204@hurleysoftware.com>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Wed, Apr 08, 2015 at 12:26:13PM -0400, Peter Hurley wrote:
> Linus,
> 
> I just got an automated bounce reply from Vinod Koul stating
> he's on vacation til April 12th, so I'd appreciate if you could
> revert this commit [1] for 4.0-final.
> 
> The commit generates a WARNING [2] in a effort to get dmaengine drivers
> to add new functionality.
> 
> I sent Vinod a note that this was happening on Beaglebone Blacks
> back on Mar 5 (-rc3). He thought the functionality would be added
> shortly, but it wasn't, so the WARNING is still happening on -rc7.

For completeness, note that this is just a warning generated at
boot. It doesn't change the previous behaviour in any way.

Any existing code will work just as well as it used to.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-04-09  7:10 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
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 [this message]

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=20150409070712.GH26727@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=balbi@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=torvalds@linux-foundation.org \
    --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).