From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>
Cc: Grygorii Strashko <grygorii.strashko@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [RFC/RFT PATCH 0/7] gpio: omap: rework and fixes
Date: Mon, 01 Jun 2015 10:14:56 -0700 [thread overview]
Message-ID: <556C9310.4000703@oracle.com> (raw)
In-Reply-To: <CACRpkdaNiZrkL0qXaxcVopm-E_18-C7OH3yMgy=5OWH3LQ7jXQ@mail.gmail.com>
On 6/1/2015 6:15 AM, Linus Walleij wrote:
> On Fri, May 22, 2015 at 9:03 PM, Tony Lindgren <tony@atomide.com> wrote:
>> * Grygorii Strashko <grygorii.strashko@linaro.org> [150522 07:37]:
>
>> Patches 1-5 seem to work for me, patch 6 does not.
>> So for patches 1-5, please feel free to add:
>>
>> Tested-by: Tony Lindgren <tony@atomide.com>
>
> OK I take this as an excuse to apply patches 1-5 with
> Tony's test tag.
>
> The maintainers can cheer in if they want, I will
> anyway take the OMAP maintainers test tag as
> a good quality indication.
>
Cheers for patch 1-5 ;-)
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
prev parent reply other threads:[~2015-06-01 17:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:35 [RFC/RFT PATCH 0/7] gpio: omap: rework and fixes Grygorii Strashko
2015-05-22 14:35 ` [PATCH 1/7] gpio: omap: fix omap_gpio_free to not clean up irq configuration Grygorii Strashko
2015-06-01 13:11 ` Linus Walleij
2015-06-02 9:31 ` Javier Martinez Canillas
2015-05-22 14:35 ` [PATCH 2/7] gpio: omap: fix error handling in omap_gpio_irq_type Grygorii Strashko
2015-06-02 9:40 ` Javier Martinez Canillas
2015-06-02 14:27 ` Grygorii.Strashko@linaro.org
2015-06-03 19:34 ` Grygorii.Strashko@linaro.org
2015-05-22 14:35 ` [RFC/RFT PATCH 3/7] gpio: omap: rework omap_x_irq_shutdown to touch only irqs specific registers Grygorii Strashko
2015-05-22 14:35 ` [RFC/RFT PATCH 4/7] gpio: omap: rework omap_gpio_request to touch only gpio " Grygorii Strashko
2015-05-22 14:35 ` [RFC/RFT PATCH 5/7] gpio: omap: rework omap_gpio_irq_startup to handle current pin state properly Grygorii Strashko
2015-05-22 14:35 ` [RFC/RFT PATCH 6/7] gpio: omap: clean up omap_gpio_irq_type Grygorii Strashko
2015-05-22 17:53 ` Tony Lindgren
2015-05-22 14:35 ` [RFC/RFT PATCH v2 7/7] gpio: omap: ensure that runtime pm will disable unused gpio banks Grygorii Strashko
2015-05-22 18:10 ` Tony Lindgren
2015-05-25 14:46 ` Grygorii.Strashko@linaro.org
2015-05-25 15:08 ` Grygorii.Strashko@linaro.org
2015-05-22 19:03 ` [RFC/RFT PATCH 0/7] gpio: omap: rework and fixes Tony Lindgren
2015-06-01 13:15 ` Linus Walleij
2015-06-01 17:14 ` santosh shilimkar [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=556C9310.4000703@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@linaro.org \
--cc=javier@dowhile0.org \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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).