From: Michael Ellerman <mpe@ellerman.id.au>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>, linuxppc-dev@ozlabs.org
Cc: stewart@linux.vnet.ibm.com
Subject: Re: [V2,1/2] powerpc/powernv: new function to access OPAL msglog
Date: Wed, 17 Feb 2016 23:41:26 +1100 (AEDT) [thread overview]
Message-ID: <20160217124126.83F60140662@ozlabs.org> (raw)
In-Reply-To: <1455002269-26543-1-git-send-email-andrew.donnellan@au1.ibm.com>
On Tue, 2016-09-02 at 07:17:48 UTC, Andrew Donnellan wrote:
> Currently, the OPAL msglog/console buffer is exposed as a sysfs file, with
> the sysfs read handler responsible for retrieving the log from the OPAL
> buffer. We'd like to be able to use it in xmon as well.
>
> Refactor the OPAL msglog code to create a new function, opal_msglog_copy(),
> that copies to an arbitrary buffer. Separate the initialisation code into
> generic memcons init and sysfs file creation.
>
> Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9b4fffa14906fce7aabf1f032d
I see you've posted a v3 since I merged this, please send an incremental patch
with the changes.
cheers
next prev parent reply other threads:[~2016-02-17 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 7:17 [PATCH V2 1/2] powerpc/powernv: new function to access OPAL msglog Andrew Donnellan
2016-02-09 7:17 ` [PATCH V2 2/2] powerpc/xmon: add command to dump " Andrew Donnellan
2016-02-11 14:15 ` Denis Kirjanov
2016-02-17 12:41 ` [V2,2/2] " Michael Ellerman
2016-02-11 6:32 ` [PATCH V2 1/2] powerpc/powernv: new function to access " Stewart Smith
2016-02-11 7:14 ` Joel Stanley
2016-02-11 7:31 ` Andrew Donnellan
2016-02-11 7:36 ` [PATCH V3 " Andrew Donnellan
2016-02-11 7:36 ` [PATCH V3 2/2] powerpc/xmon: add command to dump " Andrew Donnellan
2016-02-11 22:30 ` [PATCH V3 1/2] powerpc/powernv: new function to access " Joel Stanley
2016-02-17 12:41 ` Michael Ellerman [this message]
2016-02-18 1:17 ` [V2,1/2] " Andrew Donnellan
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=20160217124126.83F60140662@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=andrew.donnellan@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--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).