[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FFC4A23.5000107@linaro.org>
Date: Tue, 10 Jul 2012 17:28:35 +0200
From: Lee Jones <lee.jones@...aro.org>
To: Samuel Ortiz <sameo@...ux.intel.com>
CC: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
STEricsson_nomadik_linux@...t.st.com, linus.walleij@...ricsson.com,
arnd@...db.de
Subject: Re: [PATCH 1/1] mfd: ab8500: Clean-up the last two ab8500 related
DT match tables
On 10/07/12 11:13, Samuel Ortiz wrote:
> Hi Lee,
>
> On Fri, Jul 06, 2012 at 01:43:18PM +0100, Lee Jones wrote:
>> A patch was recently submitted to stop all ab8500 devices from
>> being registered through Device Tree. Instead, only the db8500
>> will be DT:ed and the rest will continue to be registered via
>> the MFD API, as they always were.
>>
>> Two patches have recently been applied which enable Device Tree
>> probing; one for rtc-ab8500 and the other for ponkey-ab8500.
>> These two need to be removed to prevent double-probing these
>> devices with Device Tree is enabled.
>>
>> Cc: Samuel Ortiz <sameo@...ux.intel.com>
>> Signed-off-by: Lee Jones <lee.jones@...aro.org>
>> ---
>> drivers/input/misc/ab8500-ponkey.c | 8 --------
>> drivers/rtc/rtc-ab8500.c | 6 ------
>> 2 files changed, 14 deletions(-)
> I don't know against which tree you generated those patches, but none of those
> 2 of_device_id arrays are in my for-next branch. So I can't apply this patch.
I can rebase them on anything of your choosing.
What is your for-next branch based on?
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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