From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754931AbbDIHKJ (ORCPT ); Thu, 9 Apr 2015 03:10:09 -0400 Received: from down.free-electrons.com ([37.187.137.238]:50811 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753410AbbDIHKE (ORCPT ); Thu, 9 Apr 2015 03:10:04 -0400 Date: Thu, 9 Apr 2015 09:09:27 +0200 From: Maxime Ripard To: Peter Hurley Cc: Vinod Koul , Felipe Balbi , Laurent Pinchart , Linux kernel Subject: Re: [4.0-rc+] WARNING: CPU: 0 PID: 1 at ./drivers/dma/dmaengine.c:863 dma_async_device_register+0xe0/0x540() Message-ID: <20150409070927.GI26727@lukather> References: <54F87075.5020105@hurleysoftware.com> <20150305161236.GG2613@intel.com> <55254EFD.10700@hurleysoftware.com> <20150408155945.GG26727@lukather> <55255232.40700@hurleysoftware.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h22Fi9ANawrtbNPX" Content-Disposition: inline In-Reply-To: <55255232.40700@hurleysoftware.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --h22Fi9ANawrtbNPX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 beh= aviour > >>> > >>> 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=20 > >> still happening on 4.0-rc7 so please revert for 4.0-final. > >=20 > > That patch isn't introducing any regression. I fail to see how that > > justifies a revert so late in the release cycle. >=20 > 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. --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --h22Fi9ANawrtbNPX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVJiWnAAoJEBx+YmzsjxAgUb0P/1VMMSEq0drIEYCRiE5YcV8q 2vrOgu4oUH/jCjqgYL8+9d/vnRQOU6QIY54SYp+EUBRp4r6YC62mR9+hwc6Uqwlu /AfCbRYpLOTB5q74cklVeTMg04TB826nv83814hjyMQxtnQuF1LvYJW6jbx6Rt6f Ici/Gd0VzTSWHqT4eua3+CjfQx48KvnjiifN4IT5A+ElC6Zx1HJXdPI65OhAEThG eSRBmndAQ3FyF3RnAQFfoxh580WOLgyhn5gXx+ZaxqQe7RwjwuEFKGq7iZu7A/38 CTYQPJuLG5LrXn6BSPAZbg7sohnqZjRpc9H5cXnZjMOjf2GWxsJlAHf0+dSE/7dd TnRGYv/k/nvsnviD5B1tstlmn++0GeVKO18UnJLq65iD8MzwS9w/mVr3WQuerEgS qjY1whXUEgd8j3BkRTZKIFSnGg6V237dnajcpi41pVblpWobLw2Ui4rvfJKQ5jNw LZP1w8FrwG4JAmxjErj7kFuVKbyvQalVSAz38nlttO/Q8WoajFXE1mu1uEdDw8lO BQNjlPyKNrIndBVi8AgfK+suw1Ot+S2pH+GJH5ioh44GWq2WeWRNABshceJwxNBn AAiFkw3DzjIM9Gvog+RSpLc5vHbB0XxK2SR9yhRMK/9bs3m0PAxEZV6FJv2Q1HBd QfYP83JGlUwWs2j3jtsn =h6z2 -----END PGP SIGNATURE----- --h22Fi9ANawrtbNPX--