linux-kernel - Re: [PATCH] mfd: max77693: Fix up bug of wrong interrupt number

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 04 Nov 2013 10:58:20 +0900
From:	Chanwoo Choi <cw00.choi@...sung.com>
To:	Chanwoo Choi <cw00.choi@...sung.com>
Cc:	sameo@...ux.intel.com, lee.jones@...aro.org,
	linux-kernel@...r.kernel.org, kyungmin.park@...sung.com
Subject: Re: [PATCH] mfd: max77693: Fix up bug of wrong interrupt number

Ping!

Thanks,
Chanwoo Choi

On 10/10/2013 10:05 AM, Chanwoo Choi wrote:
> The max77693 MFD device use irq domain method which has hardware interrupt number
> and virtual interrupt number getting through irq domain mapping. This patch
> use hardware interrupt number instead of virtual interrupt number to get
> struct irq_data.
> 
> Signed-off-by: Chanwoo Choi <cw00.choi@...sung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@...sung.com>
> ---
>  drivers/mfd/max77693-irq.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/mfd/max77693-irq.c b/drivers/mfd/max77693-irq.c
> index 1029d01..66b58fe 100644
> --- a/drivers/mfd/max77693-irq.c
> +++ b/drivers/mfd/max77693-irq.c
> @@ -128,7 +128,8 @@ static void max77693_irq_sync_unlock(struct irq_data *data)
>  static const inline struct max77693_irq_data *
>  irq_to_max77693_irq(struct max77693_dev *max77693, int irq)
>  {
> -	return &max77693_irqs[irq];
> +	struct irq_data *data = irq_get_irq_data(irq);
> +	return &max77693_irqs[data->hwirq];
>  }
>  
>  static void max77693_irq_mask(struct irq_data *data)
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/