From: Ian Campbell <Ian.Campbell@citrix.com>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
Cc: keir@xen.org, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
jbeulich@suse.com, boris.ostrovsky@oracle.com
Subject: Re: [PATCH V3] docs, amd_ucode: Add AMD container file format notes
Date: Tue, 7 Oct 2014 09:31:58 +0100 [thread overview]
Message-ID: <1412670718.4972.3.camel@citrix.com> (raw)
In-Reply-To: <1412621867-4067-1-git-send-email-aravind.gopalakrishnan@amd.com>
On Mon, 2014-10-06 at 13:57 -0500, Aravind Gopalakrishnan wrote:
> This patch introduces documentation notes about AMD container
> file formats and where to obtain latest container files from.
I think this has already been committed and is currently sitting in
staging waiting for a test pass.
next prev parent reply other threads:[~2014-10-07 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 18:57 [PATCH V3] docs, amd_ucode: Add AMD container file format notes Aravind Gopalakrishnan
2014-10-07 8:31 ` Ian Campbell [this message]
2014-10-07 13:48 ` Boris Ostrovsky
2014-10-07 13:49 ` Ian Campbell
2014-10-07 14:41 ` Aravind Gopalakrishnan
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=1412670718.4972.3.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=aravind.gopalakrishnan@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--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.