From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch 1/3] Drop tasklist lock in do_sched_setscheduler
Date: Sat, 24 Jun 2006 10:25:05 +0200 [thread overview]
Message-ID: <1151137505.25491.331.camel@localhost.localdomain> (raw)
In-Reply-To: <20060624010741.6faf355d.akpm@osdl.org>
On Sat, 2006-06-24 at 01:07 -0700, Andrew Morton wrote:
> These three patches had intricate dependencies upon the __IP__ and
> __IP_DECL__ gunk which later patches removed, so these patches do not
> compile against the pi-futex patches.
>
> So I dropped these.
>
> And I'll drop the lockdep patches, so you'll be able to redo these.
Will do.
tglx
next prev parent reply other threads:[~2006-06-24 8:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 9:08 [patch 0/3] rtmutex: Propagate priority setting into lock chains Thomas Gleixner
2006-06-22 9:08 ` [patch 1/3] Drop tasklist lock in do_sched_setscheduler Thomas Gleixner
2006-06-23 1:48 ` Andrew Morton
2006-06-23 6:01 ` Thomas Gleixner
2006-06-24 8:07 ` Andrew Morton
2006-06-24 8:25 ` Thomas Gleixner [this message]
2006-06-22 9:08 ` [patch 2/3] rtmutex: Propagate priority settings into PI lock chains Thomas Gleixner
2006-06-22 14:20 ` Steven Rostedt
2006-06-22 18:02 ` Esben Nielsen
2006-06-23 6:27 ` Steven Rostedt
2006-06-23 2:08 ` Andrew Morton
2006-06-23 9:28 ` [PATCH -mm] bug if setscheduler is called from interrupt context Steven Rostedt
2006-06-23 2:06 ` [patch 2/3] rtmutex: Propagate priority settings into PI lock chains Andrew Morton
2006-06-23 16:26 ` Thomas Gleixner
2006-06-22 9:08 ` [patch 3/3] rtmutex: Modify rtmutex-tester to test the setscheduler propagation Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2006-06-25 0:50 [patch 1/3] Drop tasklist lock in do_sched_setscheduler Oleg Nesterov
2006-06-25 15:35 ` Thomas Gleixner
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=1151137505.25491.331.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.