From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] sched/wait: Introduce new, more compact wait_event*() primitives
Date: Wed, 8 Mar 2017 12:55:05 +0100 [thread overview]
Message-ID: <20170308115505.GA17536@gmail.com> (raw)
In-Reply-To: <20170308083719.GA3251@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
> You can find the latest (WIP, frequently rebased) version in:
>
> git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core
>
> The first 10 patches reshape the waitqueue code to be more hackable (to me!),
> because I kept bumping into confusing names all the time, but the real change
> you'd be most interested in is, in an RFC (to be rebased!) form, the following
> one:
>
> 0c32c5717beb sched/wait: Introduce new, more compact wait_event*() primitives
>
> I've attached that patch below as well.
Note that I rebased it meanwhile so the SHA1's changed. The commit titles should
still be the same though.
Thanks,
Ingo
next prev parent reply other threads:[~2017-03-08 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 1:36 [GIT PULL] sched.h split-up Ingo Molnar
2017-03-03 20:13 ` Linus Torvalds
2017-03-04 7:30 ` Ingo Molnar
2017-03-07 23:33 ` Linus Torvalds
2017-03-08 0:04 ` Linus Torvalds
2017-03-08 17:24 ` Ingo Molnar
2017-03-08 8:37 ` [RFC PATCH] sched/wait: Introduce new, more compact wait_event*() primitives Ingo Molnar
2017-03-08 9:17 ` [RFC PATCH] sched/wait: Add <linux/sched/signal.h> dependency for now Ingo Molnar
2017-03-08 10:11 ` [PATCH -v2] " Ingo Molnar
2017-03-08 11:55 ` Ingo Molnar [this message]
2017-03-08 12:10 ` [RFC PATCH, -v2] sched/wait: Introduce new, more compact wait_event*() primitives Ingo Molnar
2017-03-09 16:25 ` Peter Zijlstra
2017-03-08 16:37 ` [RFC PATCH] " Linus Torvalds
2017-03-08 17:16 ` Ingo Molnar
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=20170308115505.GA17536@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 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.