From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mfd: ab8500: Clean-up the last two ab8500 related DT match tables
Date: Tue, 10 Jul 2012 18:55:18 +0200 [thread overview]
Message-ID: <20120710165518.GG15345@sortiz-mobl> (raw)
In-Reply-To: <4FFC4A23.5000107@linaro.org>
Hi Lee,
On Tue, Jul 10, 2012 at 05:28:35PM +0200, Lee Jones wrote:
> 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@linux.intel.com>
> >>Signed-off-by: Lee Jones <lee.jones@linaro.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?
On Linus' tree. And the of_device_id arrays are not there.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-07-10 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 12:43 [PATCH 1/1] mfd: ab8500: Clean-up the last two ab8500 related DT match tables Lee Jones
2012-07-09 20:48 ` Lee Jones
2012-07-10 9:13 ` Samuel Ortiz
2012-07-10 15:28 ` Lee Jones
2012-07-10 16:55 ` Samuel Ortiz [this message]
2012-07-10 18:19 ` Lee Jones
2012-07-16 12:38 ` Samuel Ortiz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120710165518.GG15345@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox