From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: rusty@rustcorp.com.au, jirislaby@gmail.com,
linux-kernel@vger.kernel.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: mmotm 2009-02-17-12-33 uploaded
Date: Tue, 28 Apr 2009 12:48:50 -0700 [thread overview]
Message-ID: <20090428124850.571c36e6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090428192219.GA3398@redhat.com>
On Tue, 28 Apr 2009 21:22:19 +0200
Oleg Nesterov <oleg@redhat.com> wrote:
> So, what happened with
>
> kthreads-simplify-the-startup-synchronization.patch
> http://marc.info/?l=linux-mm-commits&m=123335224710768
>
> kthreads-rework-kthread_stop.patch
> http://marc.info/?l=linux-mm-commits&m=123335227910835
>
> patches? Can't find them in any tree.
I seem to have had an administrative error. I think the patches were
temporarily parked because people were madly changing things under my feet,
and they didn't get unparked.
I've just restored
kthreads-simplify-the-startup-synchronization.patch
kthreads-rework-kthread_stop.patch
kthreads-simplify-migration_thread-exit-path.patch
and I'll send them out again.
I hope nothing else got lost. They're the only *kthread* patches which
I can see here.
next prev parent reply other threads:[~2009-04-28 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 20:33 mmotm 2009-02-17-12-33 uploaded akpm
2009-02-17 23:21 ` Jiri Slaby
2009-02-17 23:31 ` Andrew Morton
2009-02-18 8:45 ` Jiri Slaby
2009-02-18 9:19 ` Jiri Slaby
2009-02-18 9:35 ` Jiri Slaby
2009-02-18 9:53 ` Andrew Morton
2009-02-18 12:15 ` Rusty Russell
2009-02-18 14:50 ` Oleg Nesterov
2009-04-28 19:22 ` Oleg Nesterov
2009-04-28 19:48 ` Andrew Morton [this message]
2009-04-28 20:13 ` Oleg Nesterov
2009-02-18 0:52 ` mmotm 2009-02-17-12-33 uploaded (nr_pdflush_threads_min sysctl build error) Randy Dunlap
2009-02-18 1:40 ` Andrew Morton
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=20090428124850.571c36e6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.