[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1905537.TSPKRBptT4@vostro.rjw.lan>
Date: Tue, 04 Nov 2014 15:16:28 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Timur Tabi <timur@...eaurora.org>,
Alexandre Courbot <gnurou@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Ning Li <ning.li@...el.com>, Alan Cox <alan@...ux.intel.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
On Tuesday, November 04, 2014 02:48:27 PM Linus Walleij wrote:
> On Tue, Nov 4, 2014 at 2:31 PM, Rafael J. Wysocki <rjw@...ysocki.net> wrote:
> > On Tuesday, November 04, 2014 11:39:07 AM Mika Westerberg wrote:
>
> >> For reference the latest ACPI _DSD patches can be found here
> >>
> >> https://lkml.org/lkml/2014/10/21/762
> >
> > Actually, it's better to pull the device-properties branch:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git device-properties
> >
> > because that contains the lastest changes. It will be rebased in the future,
> > though, so don't merge it into your "immutable" branches.
>
> I've landed these two patches for v3.19, I guess we can wait for the
> device properties to land properly upstream before proceeding
> with ACPI support ...?
That would be reasonable IMO.
> Or are you guys working with one finger constantly on the fast-forward button? :D
We hoped we'd be able to get the device properties patchset in earlier.
Unfortunately, that didn't happen and is kind of blocking stuff as you can see.
Rafael
--
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