From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Alexander Shiyan <shc_work@mail.ru>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/4] gpio: syscon: reuse for keystone 2 socs
Date: Wed, 17 Sep 2014 19:05:52 +0300 [thread overview]
Message-ID: <5419B160.4030001@ti.com> (raw)
In-Reply-To: <CACRpkdaB7YpYjuND+Dic2eM=0OB0Sk=gGRRd7QrQj1Ze1MYXaQ@mail.gmail.com>
On 09/17/2014 12:43 AM, Linus Walleij wrote:
> On Wed, Sep 3, 2014 at 10:05 AM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>
>> This series intended to integrate Keystone 2 DSP GPIO controller functionality
>> into gpio-syscon driver (drivers/gpio/gpio-syscon.c) as requested
>> by Linus Walleij in [1].
>
> OK no comments on DT stuff etc for two weeks, so merged patches
> 1-3, the 4th you can take through the keystone git.
>
Thank you.
Regards,
-grygorii
WARNING: multiple messages have this Message-ID (diff)
From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] gpio: syscon: reuse for keystone 2 socs
Date: Wed, 17 Sep 2014 19:05:52 +0300 [thread overview]
Message-ID: <5419B160.4030001@ti.com> (raw)
In-Reply-To: <CACRpkdaB7YpYjuND+Dic2eM=0OB0Sk=gGRRd7QrQj1Ze1MYXaQ@mail.gmail.com>
On 09/17/2014 12:43 AM, Linus Walleij wrote:
> On Wed, Sep 3, 2014 at 10:05 AM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>
>> This series intended to integrate Keystone 2 DSP GPIO controller functionality
>> into gpio-syscon driver (drivers/gpio/gpio-syscon.c) as requested
>> by Linus Walleij in [1].
>
> OK no comments on DT stuff etc for two weeks, so merged patches
> 1-3, the 4th you can take through the keystone git.
>
Thank you.
Regards,
-grygorii
next prev parent reply other threads:[~2014-09-17 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 17:05 [PATCH v3 0/4] gpio: syscon: reuse for keystone 2 socs Grygorii Strashko
2014-09-03 17:05 ` Grygorii Strashko
2014-09-03 17:05 ` [PATCH v3 1/4] gpio: syscon: add soc specific callback to assign output value Grygorii Strashko
2014-09-03 17:05 ` Grygorii Strashko
2014-09-03 17:05 ` [PATCH v3 2/4] gpio: syscon: retrive syscon node and regs offsets from dt Grygorii Strashko
2014-09-03 17:05 ` Grygorii Strashko
2014-09-03 17:05 ` [PATCH v3 3/4] gpio: syscon: reuse for keystone 2 socs Grygorii Strashko
2014-09-03 17:05 ` Grygorii Strashko
2014-09-05 8:30 ` Linus Walleij
2014-09-05 8:30 ` Linus Walleij
2014-09-05 8:40 ` Alexander Shiyan
2014-09-05 8:40 ` Alexander Shiyan
2014-09-03 17:05 ` [PATCH v3 4/4] ARM: dts: keystone-k2hk: add dsp gpio controllers nodes Grygorii Strashko
2014-09-03 17:05 ` Grygorii Strashko
2014-09-16 21:43 ` [PATCH v3 0/4] gpio: syscon: reuse for keystone 2 socs Linus Walleij
2014-09-16 21:43 ` Linus Walleij
2014-09-17 16:05 ` Grygorii Strashko [this message]
2014-09-17 16:05 ` Grygorii Strashko
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=5419B160.4030001@ti.com \
--to=grygorii.strashko@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=shc_work@mail.ru \
/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.