From: Davidlohr Bueso <dave@stgolabs.net>
To: "Long, Wai Man" <waiman.long@hpe.com>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH -tip v2] locking/pvqspinlock: Robustify init_qspinlock_stat()
Date: Tue, 19 Apr 2016 21:13:22 -0700 [thread overview]
Message-ID: <20160420041322.GB3472@linux-uzut.site> (raw)
In-Reply-To: <20160420041048.GA3472@linux-uzut.site>
>+ pr_info("Could not create 'qlockstat' debugfs entries\n");
Please ignore this, I was not meaning to change pr_warn level, this was
simply a stale version. Sending v3 *sigh*.
next prev parent reply other threads:[~2016-04-20 4:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 6:31 [PATCH -tip 1/3] locking/pvqspinlock: Fix div by 0 in qstats Davidlohr Bueso
2016-04-18 6:31 ` [PATCH -tip 2/3] locking/pvqspinlock: Avoid double resetting of stats Davidlohr Bueso
2016-04-18 19:39 ` Waiman Long
2016-05-05 9:43 ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2016-04-18 6:31 ` [PATCH -tip 3/3] locking/pvqspinlock: Robustify init_qspinlock_stat() Davidlohr Bueso
2016-04-18 16:16 ` Davidlohr Bueso
[not found] ` <CS1PR84MB0312315E60265F5E8972CACBF16C0@CS1PR84MB0312.NAMPRD84.PROD.OUTLOOK.COM>
2016-04-20 4:10 ` [PATCH -tip v2] " Davidlohr Bueso
2016-04-20 4:13 ` Davidlohr Bueso [this message]
2016-04-20 4:17 ` [PATCH -tip v3 3/3] " Davidlohr Bueso
2016-04-20 20:06 ` Waiman Long
2016-05-05 9:44 ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2016-04-18 19:40 ` [PATCH -tip 3/3] " Waiman Long
2016-04-18 19:34 ` [PATCH -tip 1/3] locking/pvqspinlock: Fix div by 0 in qstats Waiman Long
2016-04-19 9:34 ` [tip:locking/urgent] locking/pvqspinlock: Fix division by zero in qstat_read() tip-bot for Davidlohr Bueso
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=20160420041322.GB3472@linux-uzut.site \
--to=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=waiman.long@hpe.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).