All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: boris.ostrovsky@oracle.com, keir@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH V5] x86, amd_ucode: Support multiple container files appended together
Date: Mon, 7 Jul 2014 10:37:19 -0500	[thread overview]
Message-ID: <53BABEAF.1010307@amd.com> (raw)
In-Reply-To: <53B69C860200007800020A2A@mail.emea.novell.com>

On 7/4/2014 5:22 AM, Jan Beulich wrote:
>>>> On 03.07.14 at 17:47, <aravind.gopalakrishnan@amd.com> wrote:
>> @@ -236,7 +251,14 @@ static int get_ucode_from_buffer_amd(
>>       mpbuf = (const struct mpbhdr *)&bufp[off];
>>       if ( mpbuf->type != UCODE_UCODE_TYPE )
>>       {
>> -        printk(KERN_ERR "microcode: Wrong microcode payload type field\n");
>> +        /*
>> +         * In a situation where ucode update has succeeded;
>> +         * but there is a subsequent container file being parsed,
>> +         * then, there is no need of this ERR message to be printed.
>> +         */
>> +        if ( *(const uint32_t *)buf != UCODE_MAGIC )
> Don't you need to use mpbuf here (which is equal to buf only when
> off == 0)?
Hmm. Actually, this check here can be removed as well;
after the changes in V5, we won't really hit this condition anyway.

Thanks,
-Aravind.

      reply	other threads:[~2014-07-07 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 15:47 [PATCH V5] x86, amd_ucode: Support multiple container files appended together Aravind Gopalakrishnan
2014-07-04 10:22 ` Jan Beulich
2014-07-07 15:37   ` Aravind Gopalakrishnan [this message]

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=53BABEAF.1010307@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.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.