mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Borislav Petkov <bp@amd64.org>, Greg Kroah-Hartman <greg@kroah.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>,
	Jim Cromie <jim.cromie@gmail.com>,
	Jason Baron <jbaron@redhat.com>
Subject: Re: [PATCH] init: Drop initcall level output
Date: Mon, 04 Jun 2012 12:58:58 +0930	[thread overview]
Message-ID: <87lik321s5.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1338569760-28859-1-git-send-email-bp@amd64.org>

On Fri,  1 Jun 2012 18:56:00 +0200, Borislav Petkov <bp@amd64.org> wrote:
> From: Borislav Petkov <borislav.petkov@amd.com>
> 
> 9fb48c744ba6a ("params: add 3rd arg to option handler callback
> signature") added similar lines to dmesg:
> 
> initlevel:0=early, 4 registered initcalls
> initlevel:1=core, 31 registered initcalls
> initlevel:2=postcore, 11 registered initcalls
> initlevel:3=arch, 7 registered initcalls
> initlevel:4=subsys, 40 registered initcalls
> initlevel:5=fs, 30 registered initcalls
> initlevel:6=device, 250 registered initcalls
> initlevel:7=late, 35 registered initcalls
> 
> but they don't contain any info for the general user staring at dmesg.
> I'm very doubtful the count of initcalls registered per level helps
> anyone so drop that output completely.
> 
> Cc: Jim Cromie <jim.cromie@gmail.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Jason Baron <jbaron@redhat.com>
> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>

Agreed and applied.

Thanks!
Rusty.

      reply	other threads:[~2012-06-04  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 16:56 Borislav Petkov
2012-06-04  3:28 ` Rusty Russell [this message]

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=87lik321s5.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=borislav.petkov@amd.com \
    --cc=bp@amd64.org \
    --cc=greg@kroah.com \
    --cc=jbaron@redhat.com \
    --cc=jim.cromie@gmail.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
Powered by JetHome