public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: oleg@tv-sign.ru, ebiederm@xmission.com, mingo@elte.hu,
	torvalds@linux-foundation.org, roland@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] introduce PF_KTHREAD flag
Date: Mon, 23 Jun 2008 14:52:12 -0700	[thread overview]
Message-ID: <20080623145212.c6627156.akpm@linux-foundation.org> (raw)
In-Reply-To: <200806232336.59965.rjw@sisk.pl>

On Mon, 23 Jun 2008 23:36:59 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Monday, 23 of June 2008, Andrew Morton wrote:
> > On Mon, 23 Jun 2008 13:47:06 -0700
> > Andrew Morton <akpm@linux-foundation.org> wrote:
> > 
> > > I don't yet know how much additional damage will happen as a result.
> > 
> > Lots.
> 
> Well, sorry about that.  I can ask Len to drop the freezer patch temporarily
> and rebase it on top of -next if that helps.

The freezer patch is already in linux-next.  Assuming those changes are
planned for 2.6.27 then it's best to leave things as they are.


Some of these problems will go away once I get most-of-mm into
linux-next.  But it will mean that people will need to start weaning
themselves off the practice of preparing patches against Linus
mainline.


  reply	other threads:[~2008-06-23 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 15:30 [PATCH 1/3] introduce PF_KTHREAD flag Oleg Nesterov
2008-06-03 21:14 ` Andrew Morton
2008-06-04 17:44   ` Oleg Nesterov
2008-06-23 20:40 ` Andrew Morton
2008-06-23 20:47   ` Andrew Morton
2008-06-23 20:52     ` Andrew Morton
2008-06-23 21:36       ` Rafael J. Wysocki
2008-06-23 21:52         ` Andrew Morton [this message]
2008-06-24 13:42       ` Oleg Nesterov
2008-06-24 20:51         ` Rafael J. Wysocki

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=20080623145212.c6627156.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@tv-sign.ru \
    --cc=rjw@sisk.pl \
    --cc=roland@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox