linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: suravee.suthikulpanit@amd.com (Suravee Suthikulanit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/4] gicv2m: acpi: Add ACPI support for GICv2m MSI
Date: Wed, 9 Dec 2015 21:07:25 -0600	[thread overview]
Message-ID: <5668EC6D.7020305@amd.com> (raw)
In-Reply-To: <CADaLNDkF_-6Odo6ygyuUVSNdcq93stC-pyGTXEoBDUizPzd99Q@mail.gmail.com>

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@apm.com>
>

Thanks Duc.

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

Thanks,
Suravee

  reply	other threads:[~2015-12-10  3:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 19:24 [PATCH v6 0/4] gicv2m: acpi: Add ACPI support for GICv2m MSI Suravee Suthikulpanit
2015-12-09 19:24 ` [PATCH v6 1/4] acpi: pci: Setup MSI domain for ACPI based pci devices Suravee Suthikulpanit
2015-12-09 19:24 ` [PATCH v6 2/4] irqdomain: introduce is_fwnode_irqchip helper Suravee Suthikulpanit
2015-12-09 19:24 ` [PATCH v6 3/4] gicv2m: Refactor to prepare for ACPI support Suravee Suthikulpanit
2015-12-09 19:24 ` [PATCH v6 4/4] gicv2m: acpi: Introducing GICv2m " Suravee Suthikulpanit
2015-12-10  9:14   ` Marc Zyngier
2015-12-10 16:11     ` Suravee Suthikulanit
2015-12-10  2:20 ` [PATCH v6 0/4] gicv2m: acpi: Add ACPI support for GICv2m MSI Duc Dang
2015-12-10  3:07   ` Suravee Suthikulanit [this message]
2015-12-10  9:26 ` Marc Zyngier

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=5668EC6D.7020305@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).