From: Ingo Molnar <mingo@kernel.org>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: linux-kernel@vger.kernel.org, dvhart@linux.intel.com,
peterz@infradead.org, tglx@linutronix.de,
paulmck@linux.vnet.ibm.com, efault@gmx.de, jeffm@suse.com,
torvalds@linux-foundation.org, scott.norton@hp.com,
tom.vaden@hp.com, aswin@hp.com, Waiman.Long@hp.com,
jason.low2@hp.com
Subject: Re: [PATCH v2 0/4] futex: Wakeup optimizations
Date: Thu, 19 Dec 2013 13:54:59 +0100 [thread overview]
Message-ID: <20131219125459.GB18527@gmail.com> (raw)
In-Reply-To: <1387380741.2797.27.camel@buesod1.americas.hpqcorp.net>
* Davidlohr Bueso <davidlohr@hp.com> wrote:
> ping?
>
> If no one has any objections, could this patchset be picked up?
There were a couple of review comments that I don't see fully
addressed, one of them involving the messy looking SOB chain, so a new
version needs to be sent in any case.
Thanks,
Ingo
prev parent reply other threads:[~2013-12-19 12:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 9:45 [PATCH v2 0/4] futex: Wakeup optimizations Davidlohr Bueso
2013-12-03 9:45 ` [PATCH v2 1/4] futex: Misc cleanups Davidlohr Bueso
2013-12-03 9:45 ` [PATCH v2 2/4] futex: Larger hash table Davidlohr Bueso
2013-12-03 9:45 ` [PATCH v2 3/4] futex: Document ordering guarantees Davidlohr Bueso
2013-12-03 9:45 ` [PATCH v2 4/4] futex: Avoid taking hb lock if nothing to wakeup Davidlohr Bueso
2013-12-06 18:26 ` Thomas Gleixner
2013-12-06 19:04 ` Davidlohr Bueso
2013-12-10 15:36 ` Ingo Molnar
2013-12-10 16:17 ` Davidlohr Bueso
2013-12-10 18:28 ` Ingo Molnar
2013-12-10 16:08 ` Peter Zijlstra
2013-12-10 16:24 ` Peter Zijlstra
2013-12-10 16:57 ` Peter Zijlstra
2013-12-10 17:22 ` Davidlohr Bueso
2013-12-10 17:34 ` Peter Zijlstra
2013-12-10 17:15 ` Peter Zijlstra
2013-12-10 17:36 ` Davidlohr Bueso
2013-12-10 18:00 ` Peter Zijlstra
2013-12-10 18:10 ` [PATCH v3 " Davidlohr Bueso
2013-12-12 17:30 ` [PATCH v2 0/4] futex: Wakeup optimizations Peter Zijlstra
2013-12-18 15:32 ` Davidlohr Bueso
2013-12-19 12:54 ` Ingo Molnar [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=20131219125459.GB18527@gmail.com \
--to=mingo@kernel.org \
--cc=Waiman.Long@hp.com \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=dvhart@linux.intel.com \
--cc=efault@gmx.de \
--cc=jason.low2@hp.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tom.vaden@hp.com \
--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