From: Douglas Miller <dougmill@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>,
Tejun Heo <tj@kernel.org>
Cc: linux-block@vger.kernel.org,
Douglas Miller <dougmill@linux.vnet.ibm.com>,
Guilherme Piccoli <gpiccoli@br.ibm.com>
Subject: [PATCH V2 0/1] percpu-refcount: fix reference leak during percpu-atomic transition
Date: Fri, 27 Jan 2017 17:32:15 -0600 [thread overview]
Message-ID: <1485559936-14133-1-git-send-email-dougmill@linux.vnet.ibm.com> (raw)
Removed extraneous parentheses. Did not switch to "bool" as that would necessitate
more testing and raises the question whether other platforms might have a different
definition for "bool" that would not fix this problem.
next reply other threads:[~2017-01-28 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 23:32 Douglas Miller [this message]
2017-01-27 23:32 ` [PATCH V2 1/1] percpu-refcount: fix reference leak during percpu-atomic transition Douglas Miller
2017-01-28 0:13 ` [PATCH V2 0/1] " Tejun Heo
2017-01-28 0:18 ` Douglas Miller
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=1485559936-14133-1-git-send-email-dougmill@linux.vnet.ibm.com \
--to=dougmill@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=gpiccoli@br.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).