From: Ingo Molnar <mingo@kernel.org>
To: Chen <hi3766691@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] x86/urgent fixes for v3.5
Date: Thu, 24 May 2012 19:07:15 +0200 [thread overview]
Message-ID: <20120524170715.GB21355@gmail.com> (raw)
In-Reply-To: <CANQmPXgxT3rvgGCOjztuGCTkgf4aa2-5a5q6K-8xPR1EcAsdgA@mail.gmail.com>
* Chen <hi3766691@gmail.com> wrote:
> Everyone knows that this patch had been unstable. Also, too
> much code are pushed into printk() with the patch
Interesting posts, first the "500K scheduler" nonsense now
printk nonsense?
Ingo
next prev parent reply other threads:[~2012-05-24 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 11:34 [GIT PULL] x86/urgent fixes for v3.5 Ingo Molnar
2012-05-23 17:07 ` Linus Torvalds
2012-05-23 17:13 ` H. Peter Anvin
2012-05-23 17:48 ` Ingo Molnar
2012-05-23 17:57 ` Linus Torvalds
2012-05-24 5:27 ` Ingo Molnar
2012-05-24 15:31 ` H. Peter Anvin
2012-05-24 15:44 ` Linus Torvalds
2012-05-24 15:54 ` Chen
2012-05-24 17:07 ` Ingo Molnar [this message]
2012-05-25 2:40 ` Chen
2012-05-30 7:23 ` Ingo Molnar
2012-05-24 15:48 ` Chen
2012-05-24 17:19 ` Joe Perches
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=20120524170715.GB21355@gmail.com \
--to=mingo@kernel.org \
--cc=hi3766691@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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