From: Udo Steinberg <udo@hypervisor.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2-rc1
Date: Tue, 8 Nov 2011 14:43:45 +0100 [thread overview]
Message-ID: <20111108144345.7555fa01@x220> (raw)
In-Reply-To: <CA+55aFzytqbGcOzWvYAo-EnJCeK5mFqdCF5OjMTeM5UBfeyCXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Mon, 7 Nov 2011 18:10:02 -0800 Linus Torvalds (LT) wrote:
LT> Have fun, give it a good testing. There shouldn't be anything hugely
LT> scary in there, but there *is* a lot of stuff. The fact that 3.1
LT> dragged out did mean that this ended up being one of the bigger merge
LT> windows, but I'm not feeling *too* nervous about it.
Hi,
The formatting of /proc/misc broke for cpu_dma_latency. This causes programs
reading from /proc/misc to complain. For example:
cryptsetup luksClose /dev/sdX
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
With Linux 3.2-rc1:
60 network_throughput
61 network_latency
62
236 device-mapper
237 loop-control
175 agpgart
144 nvram
231 snapshot
184 microcode
227 mcelog
63 vga_arbiter
With Linux 3.1:
60 network_throughput
61 network_latency
62 cpu_dma_latency
236 device-mapper
237 loop-control
175 agpgart
144 nvram
231 snapshot
184 microcode
227 mcelog
63 vga_arbiter
Cheers,
- Udo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-11-08 14:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 2:10 Linux 3.2-rc1 Linus Torvalds
2011-11-08 3:12 ` Al Viro
2011-11-08 4:26 ` Linus Torvalds
2011-11-08 10:52 ` Geert Uytterhoeven
2011-11-08 6:50 ` Nicholas A. Bellinger
2011-11-08 13:43 ` Udo Steinberg [this message]
2011-11-08 14:47 ` Ming Lei
2011-11-08 22:10 ` Rafael J. Wysocki
2011-11-08 14:53 ` Alessandro Suardi
2011-11-08 20:13 ` Linus Torvalds
2011-11-08 20:15 ` Matthew Garrett
2011-11-08 20:44 ` Linus Torvalds
2011-11-08 14:55 ` Nick Bowler
2011-11-08 20:23 ` Linus Torvalds
2011-11-09 7:40 ` Takashi Iwai
2011-11-09 12:03 ` Wu Fengguang
2011-11-10 11:57 ` Wu Fengguang
2011-11-08 19:06 ` Thomas Bächler
2011-11-08 23:00 ` Steven Rostedt
2011-11-08 23:53 ` Linus Torvalds
2011-11-09 8:09 ` Borislav Petkov
2011-11-09 13:11 ` Valdis.Kletnieks
2011-11-09 14:20 ` Paul Rolland
2011-11-09 23:23 ` Linus Torvalds
2011-11-09 17:18 ` Randy Dunlap
2011-11-09 17:28 ` Josh Boyer
2011-11-22 1:41 ` Boaz Harrosh
2011-11-22 16:10 ` Josh Boyer
2011-11-22 18:05 ` Alan Cox
2011-11-22 18:29 ` Boaz Harrosh
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=20111108144345.7555fa01@x220 \
--to=udo@hypervisor.org \
--cc=linux-kernel@vger.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