linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: <marc.zyngier@arm.com>, <Catalin.Marinas@arm.com>,
	<Will.Deacon@arm.com>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <Liviu.Dudau@arm.com>
Subject: Re: [PATCH 0/2] Introduce ARM GICv2m MSI(-X) support
Date: Tue, 24 Jun 2014 19:19:26 -0500	[thread overview]
Message-ID: <53AA158E.1040700@amd.com> (raw)
In-Reply-To: <20140624122639.GL10202@titan.lakedaemon.net>

On 6/24/2014 7:26 AM, Jason Cooper wrote:
> On Mon, Jun 23, 2014 at 07:32:58PM -0500, suravee.suthikulpanit@amd.com wrote:
>> This patch set introduces support for MSI(-X) in GICv2m specification,
>> which is implemented in some variation of GIC400.
>>
>> This depends on and has been tested with the V7 of "Add support for PCI in AArch64"
>> (https://lkml.org/lkml/2014/3/14/320).
>
> Is this a build, boot, or runtime dependency?
>
> thx,
>
> Jason.
>

For all of the above.

Suravee


  reply	other threads:[~2014-06-25  0:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  0:32 [PATCH 0/2] Introduce ARM GICv2m MSI(-X) support suravee.suthikulpanit
2014-06-24  0:32 ` [PATCH 1/2] arm/gic: Add binding probe for GIC400 suravee.suthikulpanit
2014-06-24 12:22   ` Jason Cooper
2014-06-24  0:33 ` [PATCH 2/2] arm/gic: Add supports for GICv2m MSI(-X) suravee.suthikulpanit
2014-06-24  9:52   ` Marc Zyngier
2014-06-25  3:04     ` Suravee Suthikulanit
2014-06-27 15:43     ` Suravee Suthikulpanit
2014-06-27 17:35       ` Marc Zyngier
2014-06-24 10:11   ` Mark Rutland
2014-06-25  2:55     ` Suravee Suthikulanit
2014-06-25  8:57       ` Mark Rutland
2014-06-24 12:19 ` [PATCH 0/2] Introduce ARM GICv2m MSI(-X) support Jason Cooper
2014-06-24 12:26 ` Jason Cooper
2014-06-25  0:19   ` Suravee Suthikulanit [this message]
2014-06-30 18:27     ` Jason Cooper
2014-06-24 14:09 ` Joel Schopp

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=53AA158E.1040700@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    /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).