From: Byungchul Park <byungchul.park@lge.com>
To: akpm@linux-foundation.org
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
akinobu.mita@gmail.com, jack@suse.cz,
torvalds@linux-foundation.org
Subject: Re: [PATCH v2] lib/spinlock_debug.c: prevent an infinite recursive cycle in spin_dump()
Date: Tue, 19 Jan 2016 10:53:56 +0900 [thread overview]
Message-ID: <20160119015356.GA9882@X58A-UD3R> (raw)
In-Reply-To: <1453078692-15291-1-git-send-email-byungchul.park@lge.com>
I missed the version change desciption when I sent this v2. This patch
worked for me. Please let me know if you have other opinions.
Changes from v1 to v2
- only change comment and commit message esp. replacing "deadlock"
with "infinite recursive cycle", since it is not an actual deadlock.
Thanks,
Byungchul
next prev parent reply other threads:[~2016-01-19 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 0:58 [PATCH v2] lib/spinlock_debug.c: prevent an infinite recursive cycle in spin_dump() Byungchul Park
2016-01-19 1:53 ` Byungchul Park [this message]
2016-01-21 8:12 ` Byungchul Park
2016-01-27 0:11 ` Andrew Morton
2016-01-27 1:13 ` Peter Hurley
2016-01-27 2:00 ` Byungchul Park
2016-01-27 2:22 ` Byungchul Park
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=20160119015356.GA9882@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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