lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <584d5be2-6961-5f65-d0d7-bc4661aa21f0@xilinx.com>
Date:   Tue, 10 Apr 2018 15:44:37 +0200
From:   Michal Simek <michal.simek@...inx.com>
To:     Rob Herring <robh@...nel.org>, Michal Simek <monstr@...str.eu>
CC:     <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/3] microblaze: remove redundant early_printk support

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@...nel.org>
> Cc: Michal Simek <monstr@...str.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ