From: Julius Werner <jwerner@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Thierry Escande <thierry.escande@collabora.com>,
Dmitry Torokhov <dtor@chromium.org>,
Aaron Durbin <adurbin@chromium.org>,
Julius Werner <jwerner@chromium.org>
Subject: [PATCH v2 0/3] Memconsole changes for new coreboot format
Date: Fri, 28 Apr 2017 13:42:22 -0700 [thread overview]
Message-ID: <20170428204225.32043-1-jwerner@chromium.org> (raw)
This series enhances the memconsole driver to work well with the new
persistent ring buffer console introduced in coreboot with
https://review.coreboot.org/#/c/18301. It needs to be applied on top of
the other memconsole patches currently queued up in char-misc-next
(ending in 049a59db34e).
Julius Werner (3):
firmware: google: memconsole: Make memconsole interface more flexible
firmware: google: memconsole: Escape unprintable characters
firmware: google: memconsole: Adapt to new coreboot ring buffer format
drivers/firmware/google/memconsole-coreboot.c | 51 +++++++++++++++++++++----
drivers/firmware/google/memconsole-x86-legacy.c | 18 +++++++--
drivers/firmware/google/memconsole.c | 46 +++++++++++++++-------
drivers/firmware/google/memconsole.h | 7 ++--
4 files changed, 96 insertions(+), 26 deletions(-)
--
2.12.2
next reply other threads:[~2017-04-28 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 20:42 Julius Werner [this message]
2017-04-28 20:42 ` [PATCH v2 1/3] firmware: google: memconsole: Make memconsole interface more flexible Julius Werner
2017-04-28 20:42 ` [PATCH v2 2/3] firmware: google: memconsole: Escape unprintable characters Julius Werner
2017-04-29 5:37 ` Greg Kroah-Hartman
2017-05-01 23:44 ` Julius Werner
2017-05-02 0:42 ` Greg Kroah-Hartman
2017-05-02 22:16 ` Julius Werner
2017-04-28 20:42 ` [PATCH v2 3/3] firmware: google: memconsole: Adapt to new coreboot ring buffer format Julius Werner
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=20170428204225.32043-1-jwerner@chromium.org \
--to=jwerner@chromium.org \
--cc=adurbin@chromium.org \
--cc=dtor@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.escande@collabora.com \
/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®