From: Paul Bolle <pebolle@tiscali.nl>
To: Jiri Kosina <trivial@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [TRIVIAL] gpio: fix comment typos 'CONFIG_GPIO_IRQCHIP'
Date: Fri, 05 Sep 2014 01:18:43 +0200 [thread overview]
Message-ID: <1409872723.5546.137.camel@x220> (raw)
In-Reply-To: <1396598372.19661.10.camel@x220>
Hi Jiri,
On Fri, 2014-04-04 at 09:59 +0200, Paul Bolle wrote:
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Untested.
>
> These two typos were introduced in commit 1425052097b5 ("gpio: add IRQ
> chip helpers in gpiolib"), which has just been merged.
>
> include/linux/gpio/driver.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
> index 1827b43..8652ab7 100644
> --- a/include/linux/gpio/driver.h
> +++ b/include/linux/gpio/driver.h
> @@ -102,7 +102,7 @@ struct gpio_chip {
>
> #ifdef CONFIG_GPIOLIB_IRQCHIP
> /*
> - * With CONFIG_GPIO_IRQCHIP we get an irqchip inside the gpiolib
> + * With CONFIG_GPIOLIB_IRQCHIP we get an irqchip inside the gpiolib
> * to handle IRQs for most practical cases.
> */
> struct irq_chip *irqchip;
> @@ -218,7 +218,7 @@ int gpiochip_irqchip_add(struct gpio_chip *gpiochip,
> irq_flow_handler_t handler,
> unsigned int type);
>
> -#endif /* CONFIG_GPIO_IRQCHIP */
> +#endif /* CONFIG_GPIOLIB_IRQCHIP */
>
> #else /* CONFIG_GPIOLIB */
Did you ever had a chance to look at this patch? It still applies to
next-20140904.
Paul Bolle
next prev parent reply other threads:[~2014-09-04 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 7:59 [PATCH] [TRIVIAL] gpio: fix comment typos 'CONFIG_GPIO_IRQCHIP' Paul Bolle
2014-09-04 23:18 ` Paul Bolle [this message]
2014-09-05 11:09 ` [PATCH] [RESEND] " Paul Bolle
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=1409872723.5546.137.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/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