From: "Josh Boyer" <jwboyer@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
"Nigel Cunningham" <nigel@nigel.suspend2.net>,
"Oleg Nesterov" <oleg@tv-sign.ru>, "Pavel Machek" <pavel@ucw.cz>
Subject: Re: [PATCH -mm 0/5] Freezer update
Date: Thu, 19 Jul 2007 11:30:54 -0500 [thread overview]
Message-ID: <625fc13d0707190930j381ea4f2x462a8269db269388@mail.gmail.com> (raw)
In-Reply-To: <20070718010353.27965df7.akpm@linux-foundation.org>
On 7/18/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > so please consider them as 2.6.23 material.
>
> The door for new 2.6.23 material shut two weeks ago. Here, at least.
So do you have a general guideline as to when you'd like patches sent
to you for the next merge window? The releases are fairly
predictable, so perhaps something like one of the later -rc candidates
for the upcoming release?
E.g. patches for 2.6.24 should be to you by 2.6.23-rc<N>?
Of course, this is assuming they go through you. I'm not trying to
complicate things. Just trying to get an understanding of how you'd
like it to work.
josh
next prev parent reply other threads:[~2007-07-19 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 7:29 Rafael J. Wysocki
2007-07-18 7:30 ` [PATCH -mm 1/5] Freezer: Document relationship with memory shrinking Rafael J. Wysocki
2007-07-18 7:40 ` Nigel Cunningham
2007-07-18 7:32 ` [PATCH -mm 2/5] Freezer: Do not sync filesystems from freeze_processes Rafael J. Wysocki
2007-07-18 7:33 ` [PATCH -mm 3/5] Freezer: Prevent new tasks from inheriting TIF_FREEZE set Rafael J. Wysocki
2007-07-18 7:41 ` Nigel Cunningham
2007-07-18 7:37 ` [PATCH -mm 4/5] Freezer: Introduce freezer-firendly waiting macros Rafael J. Wysocki
2007-07-18 7:39 ` [PATCH -mm 5/5] Freezer: Do not send signals to kernel threads Rafael J. Wysocki
2007-07-18 7:46 ` [PATCH -mm 0/5] Freezer update Nigel Cunningham
2007-07-18 8:03 ` Andrew Morton
2007-07-18 8:44 ` Rafael J. Wysocki
2007-07-21 10:56 ` Pavel Machek
2007-07-19 16:30 ` Josh Boyer [this message]
2007-07-19 17:03 ` 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=625fc13d0707190930j381ea4f2x462a8269db269388@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=oleg@tv-sign.ru \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®