From: Andrew Morton <akpm@linux-foundation.org>
To: Diego Calleja <diegocg@gmail.com>
Cc: Paul Menage <menage@google.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Improve cgroup printks
Date: Mon, 12 Nov 2007 14:12:45 -0800 [thread overview]
Message-ID: <20071112141245.1d9de09a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071110121156.a547194e.diegocg@gmail.com>
On Sat, 10 Nov 2007 12:11:56 +0100 Diego Calleja <diegocg@gmail.com> wrote:
> When I boot with the 'quiet' parameter, I see on the screen:
>
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 39.036026] Initializing cgroup subsys cpuacct
> [ 39.036080] Initializing cgroup subsys debug
> [ 39.036118] Initializing cgroup subsys ns
>
> This patch lowers the priority of those messages, adds a "cgroup: " prefix
> to another couple of printks and kills the useless reference to the source file.
>
>
> Signed-off-by: Diego Calleja <diegocg@gmail.com>
>
> --- 2.6/kernel/cgroup.c.old 2007-11-10 11:35:51.000000000 +0100
> +++ 2.6/kernel/cgroup.c 2007-11-10 11:56:46.000000000 +0100
> @@ -1,6 +1,4 @@
> /*
> - * kernel/cgroup.c
> - *
> * Generic process-grouping system.
> *
> * Based originally on the cpuset system, extracted by Paul Menage
> @@ -2200,7 +2198,7 @@ static void cgroup_init_subsys(struct cg
> {
> struct cgroup_subsys_state *css;
> struct list_head *l;
> - printk(KERN_ERR "Initializing cgroup subsys %s\n", ss->name);
> + printk("Initializing cgroup subsys %s\n", ss->name);
But this one now has no facility level at all.
I'll switch it to KERN_INFO, OK?
next prev parent reply other threads:[~2007-11-12 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 11:11 [PATCH] Improve cgroup printks Diego Calleja
2007-11-12 22:12 ` Andrew Morton [this message]
2007-11-12 23:47 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2007-11-11 22:48 Jan Engelhardt
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=20071112141245.1d9de09a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.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