All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] mfd: arizona: Fix typo in arizona_irq_map
Date: Sun, 20 Sep 2015 05:18:47 +0100	[thread overview]
Message-ID: <20150920041847.GQ3039@x1> (raw)
In-Reply-To: <1441984076-21671-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Fri, 11 Sep 2015, Charles Keepax wrote:

> The type of the data for the main Arizona IRQ chip should be struct
> arizona not struct regmap_irq_chip_data. The bug is harmless but should
> probably be corrected anyway.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>  drivers/mfd/arizona-irq.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
> index 2cac4f4..3d425e9 100644
> --- a/drivers/mfd/arizona-irq.c
> +++ b/drivers/mfd/arizona-irq.c
> @@ -169,7 +169,7 @@ static struct irq_chip arizona_irq_chip = {
>  static int arizona_irq_map(struct irq_domain *h, unsigned int virq,
>  			      irq_hw_number_t hw)
>  {
> -	struct regmap_irq_chip_data *data = h->host_data;
> +	struct arizona *data = h->host_data;
>  
>  	irq_set_chip_data(virq, data);
>  	irq_set_chip_and_handler(virq, &arizona_irq_chip, handle_simple_irq);

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2015-09-20  4:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 15:07 [PATCH] mfd: arizona: Fix typo in arizona_irq_map Charles Keepax
2015-09-20  4:18 ` Lee Jones [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=20150920041847.GQ3039@x1 \
    --to=lee.jones@linaro.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=sameo@linux.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 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.