[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4FDF2590.4010901@antcom.de>
Date: Mon, 18 Jun 2012 14:56:48 +0200
From: Roland Stigge <stigge@...com.de>
To: Alexandre Pereira da Silva <aletes.xgr@...il.com>
CC: Linus Walleij <linus.walleij@...aro.org>, cjb@...top.org,
grant.likely@...retlab.ca, rob.herring@...xeda.com,
rmk+kernel@....linux.org.uk, ulf.hansson@...ricsson.com,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
spi-devel-general@...ts.sourceforge.net
Subject: Re: [PATCH] spi: spi-pl022: Adjust probe() to of_get_named_gpio()
returning -EPROBE_DEFER
On 06/18/2012 01:51 PM, Alexandre Pereira da Silva wrote:
> On Mon, Jun 18, 2012 at 8:47 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
>> On Mon, Jun 18, 2012 at 11:20 AM, Roland Stigge <stigge@...com.de> wrote:
>>
>>> The patch to gpiolib-of.c providing -EPROBE_DEFER as a hint to defer
>>> of_get_named_gpio*() to a later probe() breaks spi-pl022.c.
>>>
>>> This patch adjusts to this change, using -EPROBE_DEFER as indication to defer.
>>>
>>> Signed-off-by: Roland Stigge <stigge@...com.de>
>>
>> Acked-by: Linus Walleij <linus.walleij@...aro.org>
>
> Acked-by: Alexandre Pereira da Silva <aletes.xgr@...il.com>
>
>>> Should this patch be joined with gpiolib-of's patch to of_get_named_gpio()? Or
>>> should they just be issued as a series?
>>
>> If it's not bisectable unless you change this in the same patch then join
>> them. Else I'd put them in a series and try to figure out a good tree for
>> merging them.
>
> Ok, so lets keep the original patch as is for now.
When Linus Acked both patches for *spi-pl022* (dt + gpio/defer fix), and
they are not yet applied, please merge them. No need to introduce
intermediate breakage.
You can keep my Signed or Acked line for exactly this.
We'll keep the patch for *gpiolib-of* separate, of course.
Thanks,
Roland
--
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