From: Julien Grall <julien.grall@linaro.org>
To: Manish Jaggi <mjaggi@caviumnetworks.com>, xen-devel@lists.xen.org
Cc: Prasun.kapoor@cavium.com, "Kumar,
Vijaya" <Vijaya.Kumar@caviumnetworks.com>,
"Stefano Stabellini (Stefano.Stabellini@citrix.com)"
<stefano.stabellini@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: RFC: [PATCH 0/3] Base PCI and Cavium ThunderX PCI platform support
Date: Fri, 20 Feb 2015 11:58:19 +0000 [thread overview]
Message-ID: <54E7215B.1080900@linaro.org> (raw)
In-Reply-To: <54E720E7.1070007@caviumnetworks.com>
On 20/02/15 11:56, Manish Jaggi wrote:
>
> On 20/02/15 5:23 pm, Julien Grall wrote:
>> Hello manish,
>>
>> On 20/02/15 11:30, Manish Jaggi wrote:
>>> This patch series adds PCI support for XEN ARM.
>>> - pci config read writes maps to xen-arm pci.c
>>> - platform support includes parsing pci device tree node and callbacks
>>> for reading writing from configuration space
>>> - placeholder code is added which is necessary for compilation
>>>
>>> Next RFC Patch set will include RFC PCI pass-through support
>> You series is not threaded and every patches missing a Signed-off-by.
>>
>> Please read http://wiki.xen.org/wiki/Submitting_Xen_Project_Patches to
>> know how to submit a patch series.
> Do we need to add Signoff in RFC patches ?
Yes, an RFC is just a different kind of patch series... We need to know
who worked on it.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-02-20 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 11:30 RFC: [PATCH 0/3] Base PCI and Cavium ThunderX PCI platform support Manish Jaggi
2015-02-20 11:53 ` Julien Grall
2015-02-20 11:56 ` Manish Jaggi
2015-02-20 11:58 ` Julien Grall [this message]
2015-02-20 12:02 ` Manish Jaggi
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=54E7215B.1080900@linaro.org \
--to=julien.grall@linaro.org \
--cc=Prasun.kapoor@cavium.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=ian.campbell@citrix.com \
--cc=mjaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.