From: Rob Herring <robh@kernel.org>
To: Michal Simek <monstr@monstr.eu>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] microblaze: remove early_printk
Date: Wed, 28 Feb 2018 16:39:34 -0600 [thread overview]
Message-ID: <20180228223937.29196-1-robh@kernel.org> (raw)
This started with removing 'linux,stdout-path' which dtc now warns
about, but I noticed the early_printk support only supports that. The
early_printk support is redundant with earlycon support since the 2
Xilinx UARTs support earlycon now.
This is compile tested only. If earlycon support has already been
tested, then this change should be harmless. AFAICT, the ioremap calls
work early before paging is up. Otherwise, fixmap support is needed.
Rob
Rob Herring (3):
microblaze: remove unnecessary prom.h includes
microblaze: remove redundant early_printk support
microblaze: dts: replace 'linux,stdout-path' with 'stdout-path'
arch/microblaze/Kconfig.debug | 8 --
arch/microblaze/boot/dts/system.dts | 2 +-
arch/microblaze/include/asm/cpuinfo.h | 2 +-
arch/microblaze/include/asm/pci.h | 1 -
arch/microblaze/include/asm/prom.h | 27 -----
arch/microblaze/kernel/Makefile | 1 -
arch/microblaze/kernel/early_printk.c | 184 ----------------------------------
arch/microblaze/kernel/misc.S | 35 -------
arch/microblaze/kernel/platform.c | 1 -
arch/microblaze/kernel/prom.c | 80 ---------------
arch/microblaze/kernel/setup.c | 12 +--
arch/microblaze/pci/indirect_pci.c | 1 -
12 files changed, 3 insertions(+), 351 deletions(-)
delete mode 100644 arch/microblaze/include/asm/prom.h
delete mode 100644 arch/microblaze/kernel/early_printk.c
--
2.14.1
next reply other threads:[~2018-02-28 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 22:39 Rob Herring [this message]
2018-02-28 22:39 ` [PATCH 1/3] microblaze: remove unnecessary prom.h includes Rob Herring
2018-02-28 22:39 ` [PATCH 2/3] microblaze: remove redundant early_printk support Rob Herring
2018-02-28 22:39 ` [PATCH 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=20180228223937.29196-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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