Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756883Ab3ENIkN (ORCPT ); Tue, 14 May 2013 04:40:13 -0400 Received: from mail-ie0-f179.google.com ([209.85.223.179]:49876 "EHLO mail-ie0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756429Ab3ENIkK (ORCPT ); Tue, 14 May 2013 04:40:10 -0400 MIME-Version: 1.0 In-Reply-To: <1368019749-19455-9-git-send-email-lee.jones@linaro.org> References: <1368019749-19455-1-git-send-email-lee.jones@linaro.org> <1368019749-19455-9-git-send-email-lee.jones@linaro.org> Date: Tue, 14 May 2013 10:40:10 +0200 Message-ID: Subject: Re: [PATCH 8/9] pinctrl: abx500: Rejiggle platform data and DT initialisation From: Linus Walleij To: Lee Jones Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Linus WALLEIJ , Srinidhi KASAGAR Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1258 Lines: 30 On Wed, May 8, 2013 at 3:29 PM, Lee Jones wrote: > A pointer to GPIO platform data is always passed to the driver now, so > there's little point in checking for 'pdata' and executing the DT case if > it's not there. The difference between booting with DT and !DT is when > booting with DT, plat_id is not populated. Thus, in the DT case we have > to use a DT match table in order to find out which platform we're > executing on. So, we're changing the semantics here to only use the > match table if no plat_id is supplied though platform data. > > Signed-off-by: Lee Jones Is this really included in the [0/9] fire alarm wrapper statement "Important ux500 fixups due for the v3.10 -rc:s"? It seems more like a random refactoring to me. The commit message fails to specify which regression this is fixing, like if it's causing an oops or so. So I've tentatively applied it to the pinctrl devel branch for v3.11 unless something comes up... Yours, Linus Walleij -- 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/