linux-kernel - Re: [PATCH v6 0/4] gicv2m: acpi: Add ACPI support for GICv2m MSI

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:	Wed, 9 Dec 2015 21:07:25 -0600
From:	Suravee Suthikulanit <suravee.suthikulpanit@....com>
To:	Duc Dang <dhdang@....com>
CC:	Marc Zyngier <marc.zyngier@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jason Cooper <jason@...edaemon.net>, <rjw@...ysocki.net>,
	Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
	Will Deacon <will.deacon@....com>,
	Catalin Marinas <Catalin.Marinas@....com>,
	Hanjun Guo <hanjun.guo@...aro.org>,
	Tomasz Nowicki <tomasz.nowicki@...aro.org>,
	G Gregory <graeme.gregory@...aro.org>,
	linux-arm <linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	<linux-acpi@...r.kernel.org>
Subject: Re: [PATCH v6 0/4] gicv2m: acpi: Add ACPI support for GICv2m MSI

On 12/9/2015 8:20 PM, Duc Dang wrote:
>> This has been tested on AMD Seattle (Overdrive) RevB system.
>> >
>> >NOTE: I have not tested ACPI GICv2m multiframe support since
>> >I don't have access to such system. Any helps are appreciated.
> Hi Suravee,
>
> I tested your v2m-multiframe-v6 branch with APM X-Gene 2 that has
> multiple GICv2m frames and it worked.
>
> Please feel free to add:
> Tested-by: Duc Dang<dhdang@....com>
>

Thanks Duc.

Marc, if you decide to add take V6 would you please also add the Tested-by?

Thanks,
Suravee
--
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/