From: Peter Hurley <peter@hurleysoftware.com>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Nathan Zimmer <nzimmer@sgi.com>
Subject: Re: [PATCH linux-next] procfs: fix rcu-lock/unlock in proc_reg_open() and proc_reg_release()
Date: Tue, 12 Mar 2013 20:06:46 -0400 [thread overview]
Message-ID: <1363133206.6887.1.camel@thor.lan> (raw)
In-Reply-To: <20130307072129.17719.81530.stgit@zurg>
On Thu, 2013-03-07 at 11:21 +0400, Konstantin Khlebnikov wrote:
> fix for a21813be23329e2788164eab532e79cb0e513cfc (linux-next)
> "procfs: improve scaling in proc"
>
> Signed-off-by: Konstantin Khlebnikov <khlebnikov@openvz.org>
> Cc: Nathan Zimmer <nzimmer@sgi.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
Konstantin,
Thanks for fixing this. Now -next boots once again :)
Regards,
Peter Hurley
prev parent reply other threads:[~2013-03-13 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 7:21 [PATCH linux-next] procfs: fix rcu-lock/unlock in proc_reg_open() and proc_reg_release() Konstantin Khlebnikov
2013-03-13 0:06 ` Peter Hurley [this message]
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=1363133206.6887.1.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nzimmer@sgi.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