From: Pranith Kumar <bobby.prani@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
Anton Blanchard <anton@samba.org>,
Neelesh Gupta <neelegup@linux.vnet.ibm.com>,
Joel Stanley <joel@jms.id.au>,
Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
Rob Herring <robh@kernel.org>,
"open list:LINUX FOR POWERPC..." <linuxppc-dev@lists.ozlabs.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] powerpc/powernv: Skip registering log region when CONFIG_PRINTK=n
Date: Thu, 22 Jan 2015 09:34:37 -0500 [thread overview]
Message-ID: <CAJhHMCDPCdeGSfGFoYcUHXQoemtmSTdsmLrS3_GOewrvNQm8kA@mail.gmail.com> (raw)
In-Reply-To: <1421903958.4598.4.camel@ellerman.id.au>
On Thu, Jan 22, 2015 at 12:19 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> On Wed, 2015-01-21 at 21:26 -0500, Pranith Kumar wrote:
>> When CONFIG_PRINTK=n, log_buf_addr_get() returns NULL and log_buf_len_get()
>> return 0. Check for these return values and skip registering the dump buffer.
>>
>> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
>> CC: Michael Ellerman <mpe@ellerman.id.au>
>> ---
>> arch/powerpc/platforms/powernv/opal.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>
> What changed since v1? I don't see anything?
>
Nothing in this patch but there is a v2 of the first patch in this
series, so had to resend this patch with a v2.
Thanks!
--
Pranith
next prev parent reply other threads:[~2015-01-22 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 2:26 [PATCH v2 1/2] printk: Add dummy routine for when CONFIG_PRINTK=n Pranith Kumar
2015-01-22 2:26 ` [PATCH v2 2/2] powerpc/powernv: Skip registering log region " Pranith Kumar
2015-01-22 5:19 ` Michael Ellerman
2015-01-22 14:34 ` Pranith Kumar [this message]
2015-01-22 22:35 ` Stewart Smith
2015-01-23 4:03 ` Pranith Kumar
2015-01-23 4:13 ` Michael Ellerman
2015-01-22 14:13 ` [PATCH v2 1/2] printk: Add dummy routine for " Petr Mladek
2015-01-22 14:17 ` Steven Rostedt
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=CAJhHMCDPCdeGSfGFoYcUHXQoemtmSTdsmLrS3_GOewrvNQm8kA@mail.gmail.com \
--to=bobby.prani@gmail.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=neelegup@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=robh@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).