From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Julien Grall <julien.grall@linaro.org>,
stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com
Cc: xen-devel@lists.xen.org
Subject: Re: [V2 2/3] amd/seattle: Add early printk message for the platform
Date: Thu, 2 Oct 2014 13:40:20 -0500 [thread overview]
Message-ID: <542D9C14.6060307@amd.com> (raw)
In-Reply-To: <542D74AB.4040003@linaro.org>
On 10/02/2014 10:52 AM, Julien Grall wrote:
> Hi Suravee,
>
> On 10/01/2014 08:51 PM, suravee.suthikulpanit@amd.com wrote:
>> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>
>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Reviewed-by: Julien Grall <julien.grall@linaro.org>
>> ---
>> xen/arch/arm/Rules.mk | 5 +++++
>> 1 file changed, 5 insertions(+)
>
>
> Just noticed, could you update docs/misc/arm/early-printk.txt to add an
> entry for your board?
>
> Thanks,
>
Done.
Suravee
next prev parent reply other threads:[~2014-10-02 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 19:51 [V2 0/3] Introduce AMD Seattle platform support suravee.suthikulpanit
2014-10-01 19:51 ` [V2 1/3] gicv2: Add compatibility id for gic-400 suravee.suthikulpanit
2014-10-01 19:51 ` [V2 2/3] amd/seattle: Add early printk message for the platform suravee.suthikulpanit
2014-10-02 15:52 ` Julien Grall
2014-10-02 18:40 ` Suravee Suthikulpanit [this message]
2014-10-01 19:51 ` [V2 3/3] amd/seattle: Initial revision of AMD Seattle support suravee.suthikulpanit
2014-10-02 10:41 ` Julien Grall
2014-10-02 19:04 ` Suravee Suthikulpanit
2014-10-02 20:37 ` Suravee Suthikulpanit
2014-10-02 21:26 ` Ian Campbell
2014-10-02 21:44 ` Julien Grall
2014-10-02 12:59 ` [V2 0/3] Introduce AMD Seattle platform support Ian Campbell
2014-10-02 15:10 ` Konrad Rzeszutek Wilk
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=542D9C14.6060307@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.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 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).