From: Stephen Boyd <swboyd@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] firmware: coreboot: Fix probe and simplify code
Date: Wed, 8 Aug 2018 10:24:12 -0700 [thread overview]
Message-ID: <20180808172414.29983-1-swboyd@chromium.org> (raw)
The first patch is a trimmed down version of patch#1 that leaves
the of_iomap() in place and just fixes the real problem of probe
not working on DT based platforms. The second patch collapses everything
into the core file to hopefully simplify code at the expense of mildly
changing the behavior on DT based platforms.
Stephen Boyd (2):
firmware: coreboot: Let OF core populate platform device
firmware: coreboot: Collapse platform drivers into bus core
drivers/firmware/google/Kconfig | 28 +++---
drivers/firmware/google/Makefile | 2 -
drivers/firmware/google/coreboot_table-acpi.c | 88 -----------------
drivers/firmware/google/coreboot_table-of.c | 82 ----------------
drivers/firmware/google/coreboot_table.c | 96 ++++++++++++++++---
drivers/firmware/google/coreboot_table.h | 6 --
6 files changed, 96 insertions(+), 206 deletions(-)
delete mode 100644 drivers/firmware/google/coreboot_table-acpi.c
delete mode 100644 drivers/firmware/google/coreboot_table-of.c
--
Sent by a computer through tubes
next reply other threads:[~2018-08-08 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 17:24 Stephen Boyd [this message]
2018-08-08 17:24 ` [PATCH v2 1/2] firmware: coreboot: Let OF core populate platform device Stephen Boyd
2018-08-09 9:15 ` Sudeep Holla
2018-08-08 17:24 ` [PATCH v2 2/2] firmware: coreboot: Collapse platform drivers into bus core Stephen Boyd
2018-08-08 19:07 ` Julius Werner
2018-08-08 23:42 ` Stephen Boyd
2018-08-09 19:33 ` kbuild test robot
2018-08-09 22:13 ` kbuild test robot
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=20180808172414.29983-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).