From: Richard Weinberger <richard@nod.at>
To: menage@google.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
cgroups@vger.kernel.org
Subject: Too early cgroup_init_early()
Date: Fri, 04 Nov 2011 18:45:39 +0100 [thread overview]
Message-ID: <4EB424C3.5030508@nod.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
Hi!
Is it really necessary to call cgroup_init_early() before
printk(KERN_NOTICE "%s", linux_banner)?
IMHO the Linux banner should be always the first line...
---8<---
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.1.0-09317-g9b89480 (rw@raccoon) (gcc version 4.5.3
20110428 [gcc-4_5-branch revision 173117] (SUSE Linux) ) #2 Fri Nov 4
18:32:15 CET 2011
--->8---
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2011-11-04 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EB424C3.5030508@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--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