mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Alexandru GOIA <alexandru.goia@cti.pub.ro>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] kernel booting messages, first line
Date: Tue, 29 Dec 2015 14:24:14 -0500	[thread overview]
Message-ID: <20151229192414.GB3873@htj.duckdns.org> (raw)
In-Reply-To: <5682D420.3030207@infradead.org>

On Tue, Dec 29, 2015 at 10:42:40AM -0800, Randy Dunlap wrote:
> On 12/28/15 17:31, Alexandru GOIA wrote:
> > What it does : first line of booting kernel, as seen in dmesg(1), will be the Linux kernel signature
> > (version, compiler, compiler hostname).
> > 
> > What it solves : it appers ahead of cgroup messages at booting.
> > 
> > This ugliness, since 3.10.x kernel.
> > 
> > 
> > So :
> > 
> > Instead of the unaesthetic lines :
> > 
> > Initializing cgroup subsys cpuset
> > Initializing cgroup subsys cpu
> > Initializing cgroup subsys cpuacct
> > Linux version 4 ...
> > 
> > 
> > ... We will have :
> > 
> > 
> > Linux version 4 ...
> > Initializing cgroup subsys cpuset
> > Initializing cgroup subsys cpu
> > Initializing cgroup subsys cpuacct
> > 
> > As normal .
...
> 
> I like the patch. Could you make it a proper kernel patch, please?

I don't know why cgroup is printing those messages to begin with.
They don't serve any purpose.  Lemme just kill them.

Thanks.

-- 
tejun

  reply	other threads:[~2015-12-29 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29  1:31 Alexandru GOIA
2015-12-29 18:42 ` Randy Dunlap
2015-12-29 19:24   ` Tejun Heo [this message]
2015-12-29 19:57     ` [PATCH] cgroup: demote subsystem init messages to KERN_DEBUG Tejun Heo

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=20151229192414.GB3873@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=alexandru.goia@cti.pub.ro \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®