linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: oliver <oohall@gmail.com>, Stewart Smith <stewart@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/boot: Add OPAL console to epapr wrappers
Date: Mon, 27 Jun 2016 21:44:40 +1000	[thread overview]
Message-ID: <1467027880.20278.74.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAOSf1CHP-PFf2nthzuPkUGZ5hcrSr2idGHDSc5XfZct7F4f7Jw@mail.gmail.com>

On Mon, 2016-06-27 at 16:51 +1000, oliver wrote:
> None of this is useful to us since we get most of this information
> from skiboot, but I'm not sure that's true for other platforms. The
> kernel boot log is fairly noisy as-is so we don't gain much from
> trimming. At the very least the other messages provide sanity checks
> that we've exited firmware and/or the bootloader without issues. I'll
> look at changing the returned error messages though, "invalid block
> type" is a pretty error useless you already know what you're looking
> for.

Right also if you crash in the kernel itself and these are your last
messages, knowing where the kernel was expanded can be useful.

Cheers,
Ben.

      reply	other threads:[~2016-06-27 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24  7:41 [PATCH] powerpc/boot: Add OPAL console to epapr wrappers Oliver O'Halloran
2016-06-24  9:34 ` kbuild test robot
2016-06-24 11:57 ` Benjamin Herrenschmidt
2016-06-24 12:45   ` oliver
2016-06-24 12:48 ` [PATCH v2] " Oliver O'Halloran
2016-06-27  4:38   ` Stewart Smith
2016-06-27  6:51     ` oliver
2016-06-27 11:44       ` Benjamin Herrenschmidt [this message]

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=1467027880.20278.74.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oohall@gmail.com \
    --cc=stewart@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).