From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Jin Yao <yao.jin@intel.com>, Aubrey Li <aubrey.li@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] pinctrl: baytrail: Add back Baytrail-T ACPI ID
Date: Thu, 22 May 2014 23:50:00 +0200 [thread overview]
Message-ID: <CACRpkdY28sT8jG750F9n6T=NBcsuvN3ZKpOtt4e4=VWDBJr_uA@mail.gmail.com> (raw)
In-Reply-To: <1400167727-20233-1-git-send-email-mika.westerberg@linux.intel.com>
On Thu, May 15, 2014 at 5:28 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> From: Jin Yao <yao.jin@intel.com>
>
> Now that the x86 dynamic IRQ allocation problem has been resolved with
> commmit 62a08ae2a576 (genirq: x86: Ensure that dynamic irq allocation does
> not conflict), we can add back Baytrail-T ACPI ID to the pinctrl driver.
>
> This makes the driver to work on Asus T100 where it is needed for several
> things like ACPI GPIO events and SD card detection.
>
> References: https://bugzilla.kernel.org/show_bug.cgi?id=68291
> Signed-off-by: Jin Yao <yao.jin@intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Patch applied with Rafael's ACK.
Applying this and 2/2 to v3.16 though, protest if there is a problem with this.
Yours,
Linus Walleij
next prev parent reply other threads:[~2014-05-22 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 15:28 [PATCH 1/2] pinctrl: baytrail: Add back Baytrail-T ACPI ID Mika Westerberg
2014-05-15 15:28 ` [PATCH 2/2] pinctrl: baytrail: Register GPIO chip after chip->to_irq is set Mika Westerberg
2014-05-22 21:47 ` Linus Walleij
2014-05-16 12:10 ` [PATCH 1/2] pinctrl: baytrail: Add back Baytrail-T ACPI ID Rafael J. Wysocki
2014-05-16 12:03 ` Mika Westerberg
2014-05-22 21:50 ` Linus Walleij [this message]
2014-05-23 7:18 ` 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='CACRpkdY28sT8jG750F9n6T=NBcsuvN3ZKpOtt4e4=VWDBJr_uA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=aubrey.li@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=yao.jin@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).