From: Michal Simek <michal.simek@xilinx.com>
To: Rob Herring <robh@kernel.org>, Michal Simek <monstr@monstr.eu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] microblaze: remove redundant early_printk support
Date: Tue, 10 Apr 2018 15:44:37 +0200 [thread overview]
Message-ID: <584d5be2-6961-5f65-d0d7-bc4661aa21f0@xilinx.com> (raw)
In-Reply-To: <20180328020700.17050-3-robh@kernel.org>
Hi Rob,
On 28.3.2018 04:06, Rob Herring wrote:
> With earlycon support now enabled, the arch specific early_printk support
> can be removed.
earlycon is not the full replacement of early_printk support as is
designed right now.
Definitely current early_printk is pretty old and contains code
duplication but it starts much earlier then earlycon.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> Cc: Michal Simek <monstr@monstr.eu>
> ---
> v2:
> - Fix booting. The setup_memory call needed to be before the
> parse_early_param call.
What's the reason for calling setup_memory before parse_early_param?
Is there any dependency?
Thanks,
Michal
next prev parent reply other threads:[~2018-04-10 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 2:06 [PATCH v2 0/3] microblaze: remove early_printk Rob Herring
2018-03-28 2:06 ` [PATCH v2 1/3] microblaze: remove unnecessary prom.h includes Rob Herring
2018-03-28 2:06 ` [PATCH v2 2/3] microblaze: remove redundant early_printk support Rob Herring
2018-04-10 13:44 ` Michal Simek [this message]
2018-04-13 14:11 ` Rob Herring
2018-04-23 10:50 ` Michal Simek
2018-04-23 16:34 ` Rob Herring
2018-03-28 2:07 ` [PATCH v2 3/3] microblaze: dts: replace 'linux,stdout-path' with 'stdout-path' Rob Herring
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=584d5be2-6961-5f65-d0d7-bc4661aa21f0@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=robh@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 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®