[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49D1A0B2.5070009@us.ibm.com>
Date: Mon, 30 Mar 2009 21:48:50 -0700
From: Darren Hart <dvhltc@...ibm.com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Sripathi Kodi <sripathik@...ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
John Stultz <johnstul@...ibm.com>,
Dinakar Guniguntala <dino@...ibm.com>,
Ulrich Drepper <drepper@...hat.com>,
Eric Dumazet <dada1@...mosbay.com>,
Ingo Molnar <mingo@...e.hu>, Jakub Jelinek <jakub@...hat.com>
Subject: Re: [tip PATCH v6 0/8] requeue pi implementation
Steven Rostedt wrote:
>
>
> On Mon, 30 Mar 2009, Darren Hart wrote:
>> Darren Hart (8):
>> RFC: futex: add requeue_pi calls
>> RFC: futex: Add requeue_futex() call
>> RFC: futex: Add FUTEX_HAS_TIMEOUT flag to restart.futex.flags
>
> I just finished reviewing the first three patches, and I don't see
> anything wrong with them. I'll review more tomorrow, but just for now, you
> can add on to the first three:
>
> Reviewed-by: Steven Rostedt <srostedt@...hat.com>
Thanks Steven!
I presume you mean the FIRST three, as in 0/8, 1/8, and 2/8 as opposed
to the top three above which would be 6/8, 7/8, and 8/8 ?
>
> -- Steve
>
>
>> RFC: rt_mutex: add proxy lock routines
>> RFC: futex: finish_futex_lock_pi()
>> RFC: futex: futex_lock_pi_atomic()
>> RFC: futex: futex_top_waiter()
>> RFC: futex: futex_wait_queue_me()
>>
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists