From: Tejun Heo <tj@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jeff Layton <jlayton@redhat.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-pm@vger.kernel.org, john@calva.com,
trond.myklebust@netapp.com, marek.belisko@gmail.com,
awilliam@redhat.com
Subject: Re: [PATCH v3 0/2] nfs/sunrpc: allow freezing of tasks with NFS calls in flight
Date: Mon, 28 Nov 2011 13:09:30 -0800 [thread overview]
Message-ID: <20111128210930.GA3858@google.com> (raw)
In-Reply-To: <201111282207.07098.rjw@sisk.pl>
Hello,
On Mon, Nov 28, 2011 at 10:07:06PM +0100, Rafael J. Wysocki wrote:
> The point is to let the patches stay in linux-next for a couple of days
> before moving them to the pm-freezer branch to see if there's any fallout (I'm
> not going to rebase pm-freezer, so fixing it will require addtional commits).
Ah.. thanks for the explanation. Yeah, I'm planning on pulling
freezer changes into cgroup for cgroup-freezer updates as doing it
separately seems to cause a lot of rather unnecessary conflicts so
keeping the branch stable would definitely be nice.
Thanks.
--
tejun
prev parent reply other threads:[~2011-11-28 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 20:01 [PATCH v3 0/2] nfs/sunrpc: allow freezing of tasks with NFS calls in flight Jeff Layton
2011-11-28 20:01 ` [PATCH v3 1/2] sunrpc: make rpc_wait_bit_killable handle freeze events Jeff Layton
2011-11-28 20:39 ` Tejun Heo
2011-11-28 20:01 ` [PATCH v3 2/2] nfs: make TASK_KILLABLE sleeps attempt to freeze Jeff Layton
2011-11-28 20:22 ` [PATCH v3 0/2] nfs/sunrpc: allow freezing of tasks with NFS calls in flight Rafael J. Wysocki
2011-11-28 20:40 ` Tejun Heo
2011-11-28 21:07 ` Rafael J. Wysocki
2011-11-28 21:09 ` Tejun Heo [this message]
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=20111128210930.GA3858@google.com \
--to=tj@kernel.org \
--cc=awilliam@redhat.com \
--cc=jlayton@redhat.com \
--cc=john@calva.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=rjw@sisk.pl \
--cc=trond.myklebust@netapp.com \
/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.