From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Borislav Petkov <bp@amd64.org>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org,
hpa@zytor.com
Subject: Re: [PATCH] x86: fix error paths in microcode_init()
Date: Fri, 02 Dec 2011 22:21:01 +0530 [thread overview]
Message-ID: <4ED901F5.3080302@linux.vnet.ibm.com> (raw)
In-Reply-To: <4ED90EBF02000078000652BE@nat28.tlf.novell.com>
On 12/02/2011 10:15 PM, Jan Beulich wrote:
>>>> On 02.12.11 at 17:40, "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
>> And if Boris is indeed going to take this patch, Jan, feel free to add
>> your "Signed-off-by" (if you agree to the code below) since I would like
>> to give due credit to you for pointing out the missing parts.
>
> Feel free to add that or an acked-by.
Wow! Good to know that we have an agreement :-)
Boris, it is again up to you to choose among the two(Signed-off-by or Acked-by)
for Jan. Hehe ;-)
Thanks,
Srivatsa S. Bhat
next prev parent reply other threads:[~2011-12-02 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 12:35 [PATCH] x86 Microcode: Fix the failure path of microcode update driver init code Srivatsa S. Bhat
2011-11-07 18:02 ` Borislav Petkov
2011-12-02 13:35 ` [PATCH] x86: fix error paths in microcode_init() Jan Beulich
2011-12-02 14:35 ` Borislav Petkov
2011-12-02 14:53 ` Jan Beulich
2011-12-02 15:15 ` Srivatsa S. Bhat
2011-12-02 15:24 ` Borislav Petkov
2011-12-02 15:33 ` Jan Beulich
2011-12-02 16:40 ` Srivatsa S. Bhat
2011-12-02 16:45 ` Jan Beulich
2011-12-02 16:51 ` Srivatsa S. Bhat [this message]
2011-12-02 19:45 ` Borislav Petkov
2011-12-02 20:00 ` Srivatsa S. Bhat
2011-12-05 17:39 ` [tip:x86/urgent] x86, microcode: Fix the failure path of microcode update driver init code tip-bot for Srivatsa S. Bhat
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=4ED901F5.3080302@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=JBeulich@suse.com \
--cc=bp@amd64.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.