linux-kernel - Re: [PATCH V3 0/2] irqchip: gic: Add support for GIC v2 bypass disable

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:	Tue, 8 Jul 2014 18:45:35 -0400
From:	Jason Cooper <jason@...edaemon.net>
To:	Feng Kan <fkan@....com>
Cc:	tglx@...utronix.de, marc.zyngier@....com,
	linux-kernel@...r.kernel.org, patches@....com
Subject: Re: [PATCH V3 0/2] irqchip: gic: Add support for GIC v2 bypass
 disable

Feng,

On Wed, Jul 02, 2014 at 02:18:57PM -0700, Feng Kan wrote:
> This patch series cleans up hex number in the gic driver and then adds
> the code to preserve GIC v2 bypass disable bits in the GIC driver.
> 
> V3 Change: remove incorrect Signoff by 
> 
> V2 Change:
> 	seem my send email was not working correctly, resending this with
>         rebase pull.
> 	- had to pull HaoJian's change out of arm-gic.h to keep consistency.
> 	- replace GIC defines as noted by Marc
> 	- remove GIC_CPU_DISABLE since it no longer used.
> 	- fix gic_cpu_if_down as noted by Marc
> 
> Feng Kan (2):
>   irqchip: gic: replace hex numbers with defines.
>   irqchip: gic: preserve gic V2 bypass bits in cpu ctrl register
> 
>  drivers/irqchip/irq-gic.c       | 83 +++++++++++++++++++++++++++++++----------
>  include/linux/irqchip/arm-gic.h |  2 -
>  2 files changed, 63 insertions(+), 22 deletions(-)

I'm collecting all of the various changes to the gic driver into a
single branch:

  git://git.infradead.org/users/jcooper/linux.git irqchip/gic

Please rebase your changes an top of that and resend.

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/