From: Borislav Petkov <bp@suse.de>
To: Andres Freund <andres@anarazel.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/2] x86: Fix typo preventing msr_set/clear_bit from having an effect
Date: Fri, 9 May 2014 12:46:58 +0200 [thread overview]
Message-ID: <20140509104658.GD16058@pd.tnic> (raw)
In-Reply-To: <20140509103942.GA30231@awork2.anarazel.de>
On Fri, May 09, 2014 at 12:39:42PM +0200, Andres Freund wrote:
> It got caught before the release, so all is well...
Yeah.
> Actually rather surprised it only causes relatively minor problems;
> i.e. still boots.
Well, I did switch only a couple of sites in intel.c, maybe you got
lucky... (if that can be called getting lucky at all :-P).
> Did I CC the correct people for this to get picked up for 3.15 or to I
> need to do anything else?
Yes, you did, it looks good.
Thanks!
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-05-09 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 1:29 Andres Freund
2014-05-09 1:29 ` [PATCH 1/2] x86: Fix typo preventing msr_set/clear_bit from having an effect Andres Freund
2014-05-09 7:54 ` Borislav Petkov
2014-05-09 10:39 ` Andres Freund
2014-05-09 10:46 ` Borislav Petkov [this message]
2014-05-09 16:31 ` [tip:x86/urgent] x86: Fix typo preventing msr_set/ clear_bit " tip-bot for Andres Freund
2014-05-09 1:29 ` [PATCH 2/2] x86: Fix typo in MSR_IA32_MISC_ENABLE_LIMIT_CPUID macro Andres Freund
2014-05-09 7:57 ` Borislav Petkov
2014-05-09 10:33 ` Borislav Petkov
2014-05-09 17:02 ` Joe Perches
2014-05-09 21:31 ` [PATCH] checkpatch: Warn on #defines ending in semicolon Joe Perches
2014-05-09 21:47 ` Thomas Gleixner
2014-05-09 21:59 ` Joe Perches
2014-05-09 16:31 ` [tip:x86/urgent] x86: Fix typo in MSR_IA32_MISC_ENABLE_LIMIT_CPUID macro tip-bot for Andres Freund
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=20140509104658.GD16058@pd.tnic \
--to=bp@suse.de \
--cc=andres@anarazel.de \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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