Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753894AbbFIXVE (ORCPT ); Tue, 9 Jun 2015 19:21:04 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:50993 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752181AbbFIXUv (ORCPT ); Tue, 9 Jun 2015 19:20:51 -0400 Date: Wed, 10 Jun 2015 00:20:29 +0100 From: Mark Brown To: Russell King - ARM Linux Cc: Rob Herring , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, arm@kernel.org, Greg Kroah-Hartman Message-ID: <20150609232029.GB14071@sirena.org.uk> References: <1433874401-27161-1-git-send-email-robh@kernel.org> <1433874401-27161-3-git-send-email-robh@kernel.org> <20150609191211.GA14071@sirena.org.uk> <20150609212709.GJ7557@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SkVhr1N513l62upp" Content-Disposition: inline In-Reply-To: <20150609212709.GJ7557@n2100.arm.linux.org.uk> X-Cookie: The end of labor is to gain leisure. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 02/15] regmap: kill off set_irq_flags usage X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1840 Lines: 46 --SkVhr1N513l62upp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 09, 2015 at 10:27:09PM +0100, Russell King - ARM Linux wrote: > It's because there exist platforms where specific IRQs are permanently > asserted, and unexpectedly claiming such an interrupt (eg, through IRQ > probing) would lock the system - at least before we ended up with the > detection in genirq (which has its roots in the ARM code.) Ah, yes - now I remember. I just had a vauge recollection of broken probing. > I'd suggest people think carefully about applying these patches. They > have only been around for a matter of hours, so to rush to apply them > when they haven't been revewied as a whole to assess whether the approach > is the right one is rather hasty. I'm fairly comfortable with the patch for regmap as that code is architecture neutral, should already have been consistent and the non-ARM path has definitely been tested (I've done it myself). --SkVhr1N513l62upp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVd3S9AAoJECTWi3JdVIfQvloH/3FQzEf/td+5yJDXtpYw6Jhr ZwrDhHZgpv3oI4raLuWqZtsBDVGxK0lhVBECW6FxEa4a8k8AswtqMAmReJLvrCj9 QARGTKWBDOhO9yZ+EiUP14lhhqIhF6BfroelVb/yfuCQk6mt0lMQBPcCsB0tTEfK yTK6h0d18RFIwoeTh9Q1Ri5STWXmH3ptIBsCXRr8maIR7YQE1pC2O9S6WzmpSjul o/qYTJXGbEpY64c/qUBTdpQxmoJZUvXNFHu+x2R3suk+gTcp+OLBADRIwLATjDNi 6tqafCdnoFWrK3LphCM7DXKxE8c0LrJFvp1oMfkSWLN37NvW+irmiWYNY6S8Fe4= =0PNl -----END PGP SIGNATURE----- --SkVhr1N513l62upp-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/