linux-kernel - Re: [PATCH] irqchip: atmel-aic-common: prevent clobbering of priority when changing IRQ type

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>] [day] [month] [year] [list]

Date:	Wed, 7 Jan 2015 07:51:34 -0500
From:	Jason Cooper <jason@...edaemon.net>
To:	gavinli@...gavinli.com
Cc:	tglx@...utronix.de, linux@...im.org.za, nicolas.ferre@...el.com,
	plagnioj@...osoft.com, Gavin Li <git@...gavinli.com>,
	Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irqchip: atmel-aic-common: prevent clobbering of
 priority when changing IRQ type

Gavin,

On Tue, Jan 06, 2015 at 06:47:23PM -0800, gavinli@...gavinli.com wrote:
> From: Gavin Li <git@...gavinli.com>
> 
> This patch makes the bitmask for AIC_SRCTYPE consistent
> with that of its valid values, and prevents the priority
> field at bits 2:0 from being clobbered by an incorrect
> AND with the AIC_SRCTYPE mask.
> 
> Signed-off-by: Gavin Li <gavinli@...gavinli.com>
> ---
>  drivers/irqchip/irq-atmel-aic-common.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Well done.  For a first patch this is really good.  The only thing you
missed was who/which MLs to Cc.  In the future, you can use
./scripts/get_maintainer.pl to find this info.

Applied to irqchip/urgent with Acks from the atmel maintainers and Cc'd
to stable for v3.17+

This will be in linux-next tonight if Stephen builds one.

thx,

Jason.
--
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/