From: Pavel Machek <pavel@ucw.cz>
To: Alexandru GOIA <alexandru.goia@cti.pub.ro>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] first line in booting the kernel
Date: Mon, 4 Jan 2016 21:11:41 +0100 [thread overview]
Message-ID: <20160104201141.GB5723@amd> (raw)
In-Reply-To: <DB5PR01MB106208C72E8793B9D33E9188ACE70@DB5PR01MB1062.eurprd01.prod.exchangelabs.com>
On Thu 2015-12-24 09:55:14, 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.
Acked-by: Pavel Machek <pavel@ucw.cz>
(And I guess we need your sign-off, and probably Cc:
trivial@kernel.org).
> <code>
> --- linux-4.4-rc6/init/main.c.original 2015-12-24 09:55:58.208811356 +0200
> +++ linux-4.4-rc6/init/main.c 2015-12-24 09:57:06.364813237 +0200
> @@ -513,6 +513,8 @@
> */
> boot_init_stack_canary();
>
> + pr_notice("%s", linux_banner);
> +
> cgroup_init_early();
>
> local_irq_disable();
> @@ -524,7 +526,6 @@
> */
> boot_cpu_init();
> page_address_init();
> - pr_notice("%s", linux_banner);
> setup_arch(&command_line);
> mm_init_cpumask(&init_mm);
> setup_command_line(command_line);
>
> </code>--
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2016-01-04 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 9:55 [PATCH 1/1] first line in booting the kernel Alexandru GOIA
2016-01-04 20:11 ` Pavel Machek [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=20160104201141.GB5723@amd \
--to=pavel@ucw.cz \
--cc=alexandru.goia@cti.pub.ro \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.