From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aravind Gopalakrishnan Subject: Re: [PATCH] docs, amd_ucode: Condense amd_ucode notes Date: Fri, 10 Oct 2014 09:52:44 -0500 Message-ID: <5437F2BC.9070608@amd.com> References: <1412721256-6561-1-git-send-email-aravind.gopalakrishnan@amd.com> <5437A45F020000780003D837@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5437A45F020000780003D837@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: keir@xen.org, ian.campbell@citrix.com, andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org, boris.ostrovsky@oracle.com List-Id: xen-devel@lists.xenproject.org On 10/10/2014 2:18 AM, Jan Beulich wrote: >>>> On 08.10.14 at 00:34, wrote: >> Some cleanups to the documentation- >> - Remove unnecessary steps listed to apply ucode using initrd. >> - Condense 'Misc notes' section as well >> >> Suggested-by: Boris Ostrovsky >> Signed-off-by: Aravind Gopalakrishnan >> --- >> docs/misc/amd-ucode-container.txt | 41 +++++++++++++-------------------------- >> 1 file changed, 14 insertions(+), 27 deletions(-) >> >> diff --git a/docs/misc/amd-ucode-container.txt b/docs/misc/amd-ucode-container.txt >> index ae3ceb0..b51b034 100644 >> --- a/docs/misc/amd-ucode-container.txt >> +++ b/docs/misc/amd-ucode-container.txt >> @@ -16,7 +16,7 @@ Intro to AMD Container Files: >> processor families 10h, 11h, 12h, 14h, and 15h. >> * There is one single file (container file) containing all microcode patches >> for AMD families 10h - 14h processors. [microcode_amd.bin] >> -* For AMD family 15h processors there is a separate container file. [microcode_amd_fam15h.bin] >> +* For AMD processor families 15h+, there is a separate container file. [microcode_amd_fam15h+.bin] > That replacement is not really suitable in a file name. Saying "[e.g. ..." > similarly to how it is being done further down would seem more useful. > > Hmm. Ok, I have reworded this to try to address yours and Boris' concerns. Sending it out as V2. Thanks, -Aravind.