From: "Stefan Kuhne" <stefan.kuhne@gmx.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Features and bug fixes for Linux kernel 3.3
Date: Mon, 09 Jan 2012 19:59:04 +0100 [thread overview]
Message-ID: <4F0B38F8.6050305@access.denied> (raw)
In-Reply-To: <20120109183304.GA1287@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 313 bytes --]
Am 09.01.2012 19:33, schrieb Konrad Rzeszutek Wilk:
Hello,
> Linux 3.3 merge window opened last week and today I've asked Linus
> to pulled some of the patches. This is what is going in through
> the Xen tree:
>
it sounds like no acpi/cpufreq Support in 3.3.
Is it rigth?
Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-09 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 18:33 Features and bug fixes for Linux kernel 3.3 Konrad Rzeszutek Wilk
2012-01-09 18:59 ` Stefan Kuhne [this message]
2012-01-09 21:13 ` Konrad Rzeszutek Wilk
2012-01-09 21:32 ` Konrad Rzeszutek Wilk
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=4F0B38F8.6050305@access.denied \
--to=stefan.kuhne@gmx.net \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).