From: Alexandre Courbot <gnurou@gmail.com>
To: "Chang, Rebecca Swee Fun" <rebecca.swee.fun.chang@intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
GPIO Subsystem Mailing List <linux-gpio@vger.kernel.org>,
"Westerberg, Mika" <mika.westerberg@intel.com>,
Denis Turischev <denis.turischev@compulab.co.il>
Subject: Re: [PATCHv4 3/3] gpio: sch: Enable IRQ support for Quark X1000
Date: Thu, 4 Dec 2014 17:47:05 +0900 [thread overview]
Message-ID: <CAAVeFuKFHoEFYa7FizROTwQLOPqHO0ArAMJC8t7tzEYgMcV05Q@mail.gmail.com> (raw)
In-Reply-To: <50B33AC5ED75F74F991980326F1C438D0FC6DDED@PGSMSX108.gar.corp.intel.com>
On Wed, Dec 3, 2014 at 11:26 AM, Chang, Rebecca Swee Fun
<rebecca.swee.fun.chang@intel.com> wrote:
> Hi Linus,
> Noted, while I continue to work on this IRQ feature, can I resend patch 1 and patch 2 (rebase to devel branch) in v5 thread so that you can pull them in first?
Yes, please do so. The first two patches are independant from this
feature and it will allow everyone to get them off their head.
prev parent reply other threads:[~2014-12-04 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 4:47 [PATCHv4 0/3] Enable Quark X1000 support in gpio-sch Chang Rebecca Swee Fun
2014-11-26 4:47 ` [PATCHv4 1/3] gpio: sch: Consolidate similar algorithms Chang Rebecca Swee Fun
2014-11-28 10:54 ` Mika Westerberg
2014-11-28 13:54 ` Linus Walleij
2014-11-28 13:57 ` Linus Walleij
2014-12-04 8:43 ` Alexandre Courbot
2014-11-26 4:47 ` [PATCHv4 2/3] gpio: sch: Add support for Intel Quark X1000 SoC Chang Rebecca Swee Fun
2014-12-04 8:45 ` Alexandre Courbot
2014-11-26 4:48 ` [PATCHv4 3/3] gpio: sch: Enable IRQ support for Quark X1000 Chang Rebecca Swee Fun
2014-11-27 10:53 ` Andy Shevchenko
2014-11-28 11:05 ` Mika Westerberg
2014-11-28 14:02 ` Linus Walleij
2014-12-03 2:26 ` Chang, Rebecca Swee Fun
2014-12-04 8:47 ` Alexandre Courbot [this message]
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=CAAVeFuKFHoEFYa7FizROTwQLOPqHO0ArAMJC8t7tzEYgMcV05Q@mail.gmail.com \
--to=gnurou@gmail.com \
--cc=denis.turischev@compulab.co.il \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=rebecca.swee.fun.chang@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).