From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Raymond Tan <raymond.tan@intel.com>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>
Subject: Re: [PATCH v1 1/1] gpio: dwapb: enable for Quark
Date: Tue, 17 Mar 2015 13:20:30 +0100 [thread overview]
Message-ID: <CACRpkdbcgJA4x_Xub_J2TiV6_uFD1x5EOwCxpQ3OgpzD=DFFTg@mail.gmail.com> (raw)
In-Reply-To: <1425573965-6971-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Thu, Mar 5, 2015 at 5:46 PM, Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
> The Intel Quark SoC contains the DW GPIO on board. While fixing the build error
> the commit 1972c97db5b0 (gpio: dwapb: fix compile errors) disables the
> possibility to build the driver on X86, i.e. Intel Quark.
>
> The patch reenables it for Intel Quark as well.
>
> Since we have Intel Quark SoC introduced in 4.0-rc1 I would like to make this
> fix available there as well, though the actual MFD driver [1] is not yet
> applied.
>
> [1] https://lkml.org/lkml/2015/2/1/217
>
> Fixes: 1972c97db5b0 (gpio: dwapb: fix compile errors)
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Sorry commit b90f8f22ed86f4f1a38dd2178c4be558c0c70fb9
"gpio: dwapb: re-enable GPIO_DWAPB for arm64"
conflicts, re-enabling it for ARM64.
Can you rebase ... part of me just wanna enable this driver
for the whole world, don't see why we need to narrow it down
so much.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-03-17 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 16:46 [PATCH v1 1/1] gpio: dwapb: enable for Quark Andy Shevchenko
2015-03-17 12:20 ` Linus Walleij [this message]
2015-03-17 12:28 ` Andy Shevchenko
2015-03-17 12:31 ` Shevchenko, Andriy
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='CACRpkdbcgJA4x_Xub_J2TiV6_uFD1x5EOwCxpQ3OgpzD=DFFTg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=boon.leong.ong@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=raymond.tan@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).