From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Keerthy <j-keerthy@ti.com>, <linus.walleij@linaro.org>,
<t-kristo@ti.com>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<gnurou@gmail.com>
Subject: Re: [PATCH 1/3] gpio: davinci: Remove unwanted blank line
Date: Wed, 11 Jan 2017 11:37:24 -0600 [thread overview]
Message-ID: <3ada0b60-01fb-93b9-e369-3a628ecf5fdc@ti.com> (raw)
In-Reply-To: <1484110841-2391-2-git-send-email-j-keerthy@ti.com>
On 01/10/2017 11:00 PM, Keerthy wrote:
> Remove redundant blank line.
i think it's better to drop this patch ;)
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
> include/linux/platform_data/gpio-davinci.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/platform_data/gpio-davinci.h b/include/linux/platform_data/gpio-davinci.h
> index 44ca530..18127c4 100644
> --- a/include/linux/platform_data/gpio-davinci.h
> +++ b/include/linux/platform_data/gpio-davinci.h
> @@ -26,7 +26,6 @@ struct davinci_gpio_platform_data {
> u32 gpio_unbanked;
> };
>
> -
> struct davinci_gpio_controller {
> struct gpio_chip chip;
> struct irq_domain *irq_domain;
>
--
regards,
-grygorii
next prev parent reply other threads:[~2017-01-11 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 5:00 [PATCH 0/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Keerthy
2017-01-11 5:00 ` [PATCH 1/3] gpio: davinci: Remove unwanted blank line Keerthy
2017-01-11 17:37 ` Grygorii Strashko [this message]
2017-01-12 1:53 ` Keerthy
2017-01-11 5:00 ` [PATCH 2/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Keerthy
2017-01-11 17:53 ` Grygorii Strashko
2017-01-12 2:00 ` Keerthy
2017-01-12 19:06 ` Grygorii Strashko
2017-01-13 3:42 ` Keerthy
2017-01-11 5:00 ` [PATCH 3/3] gpio: davinci: Add support for multiple GPIO controllers Keerthy
2017-01-17 14:52 ` [PATCH 0/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip Linus Walleij
2017-01-17 16:14 ` Keerthy
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=3ada0b60-01fb-93b9-e369-3a628ecf5fdc@ti.com \
--to=grygorii.strashko@ti.com \
--cc=gnurou@gmail.com \
--cc=j-keerthy@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-kristo@ti.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).