[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <89abf03242a4e5a39fab1373c62dce13@agner.ch>
Date: Thu, 05 Mar 2015 00:23:09 +0100
From: Stefan Agner <stefan@...er.ch>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
linus.walleij@...aro.org
Cc: Shawn Guo <shawn.guo@...aro.org>, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, kernel@...gutronix.de,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] pinctrl: imx: do not implicitly set pin regs to -1
On 2015-03-02 16:53, Uwe Kleine-König wrote:
> Hello,
>
> On Mon, Mar 02, 2015 at 02:42:01PM +0100, Stefan Agner wrote:
>> On 2015-03-02 13:59, Uwe Kleine-König wrote:
>> > On Mon, Mar 02, 2015 at 07:45:17PM +0800, Shawn Guo wrote:
>> >> On Fri, Feb 06, 2015 at 05:30:56PM +0100, Stefan Agner wrote:
>> >> > Commit 3dac1918a491 ("pinctrl: imx: detect uninitialized pins") needs
>> >> > the values in struct imx_pin_reg to be -1. This has been done in a
>> >> > rather unorthodox way by setting the memory to 0xff using memset...
>> >> > Use a proper for loop to initialize the whole array with -1.
>> >> >
>> >> > Signed-off-by: Stefan Agner <stefan@...er.ch>
>> >>
>> >> Acked-by: Shawn Guo <shawn.guo@...aro.org>
>> > too late. This patch is part of 4.0-rc1 (4ff0f034e95d).
>>
>> This is not the same patch. The patch you are mentioning is actually
>> fixing a bug introduce in the change where we set -1 for uninitialized
>> pins. This patch is solving the weird assignment of the initial value...
> ah right.
Do you generally agree to that change?
@Linus Walleij, anything holding this patch back from getting merged?
--
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists