From: Michael Ellerman <mpe@ellerman.id.au>
To: Li Zhong <zhong@linux.vnet.ibm.com>,
PowerPC email list <linuxppc-dev@lists.ozlabs.org>
Cc: Paul Mackerras <paulus@samba.org>
Subject: Re: [powerpc] init nvram_pstore_info's buf_lock
Date: Tue, 18 Nov 2014 15:33:14 +1100 (AEDT) [thread overview]
Message-ID: <20141118043314.4517C14011D@ozlabs.org> (raw)
In-Reply-To: <1416192750.3375.7.camel@TP420>
On Mon, 2014-17-11 at 02:52:30 UTC, Li Zhong wrote:
> It seems nvram_pstore_info's buf_lock is not initialized before
> registering, which causes some strange behavior when trying to obtain
> the lock during kdump process.
What kind of strange behaviour? Does it still work and just print a warning?
It's static, so I'd expect it to be unlocked by default.
cheers
next prev parent reply other threads:[~2014-11-18 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 2:52 [PATCH powerpc] init nvram_pstore_info's buf_lock Li Zhong
2014-11-18 4:33 ` Michael Ellerman [this message]
2014-11-18 6:12 ` [powerpc] " Li Zhong
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=20141118043314.4517C14011D@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=zhong@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).