From: Timur Tabi <timur@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Alexandre Courbot <gnurou@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Ning Li <ning.li@intel.com>, Alan Cox <alan@linux.intel.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
Date: Tue, 04 Nov 2014 10:37:12 -0600 [thread overview]
Message-ID: <545900B8.3030705@codeaurora.org> (raw)
In-Reply-To: <CACRpkdaZYubzEKVKiG4vCnh2kDr7CfRvaXcJNHSFtSUaRdXW4A@mail.gmail.com>
On 11/04/2014 07:48 AM, Linus Walleij wrote:
> 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 ...? Or are you guys working with one finger
> constantly on the fast-forward button? :D
I'll consider any ACPI enhancements as soon as they're more-or-less
stable, although I prefer to wait until they're in linux-next.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2014-11-04 16:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 11:01 [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Mika Westerberg
2014-11-03 11:01 ` [PATCH v2 1/2] gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod() Mika Westerberg
2014-11-04 10:18 ` Linus Walleij
2014-11-03 11:01 ` [PATCH v2 2/2] pinctrl: Add Intel Cherryview/Braswell pin controller support Mika Westerberg
2014-11-04 10:23 ` Linus Walleij
2014-11-03 23:24 ` [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Timur Tabi
2014-11-04 8:20 ` Mika Westerberg
2014-11-04 9:39 ` Mika Westerberg
2014-11-04 13:31 ` Rafael J. Wysocki
2014-11-04 13:48 ` Linus Walleij
2014-11-04 14:16 ` Rafael J. Wysocki
2014-11-04 14:12 ` Mika Westerberg
2014-11-04 16:37 ` Timur Tabi [this message]
2014-11-04 21:51 ` Timur Tabi
2014-11-04 22:47 ` Rafael J. Wysocki
2014-11-04 22:32 ` Timur Tabi
2014-11-04 22:39 ` Timur Tabi
2014-11-04 23:13 ` Rafael J. Wysocki
2014-11-04 22:56 ` Timur Tabi
2014-11-04 23:18 ` Timur Tabi
2014-11-05 21:04 ` Rafael J. Wysocki
2014-11-05 21:19 ` Rafael J. Wysocki
2014-11-04 23:00 ` Rafael J. Wysocki
2014-11-04 17:54 ` Timur Tabi
2014-11-04 19:04 ` Mika Westerberg
2014-11-06 19:30 ` Linus Walleij
2014-11-05 21:46 ` Grant Likely
2014-11-05 21:59 ` Timur Tabi
2014-11-05 22:15 ` Rafael J. Wysocki
2014-11-06 17:37 ` Grant Likely
2014-11-06 18:01 ` Timur Tabi
2014-11-07 23:12 ` Timur Tabi
2014-11-06 19:28 ` Linus Walleij
2014-11-05 21:44 ` Olof Johansson
2014-11-06 6:07 ` Mika Westerberg
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=545900B8.3030705@codeaurora.org \
--to=timur@codeaurora.org \
--cc=alan@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=ning.li@intel.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.