From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Lin Ming <lin@ming.vg>
Cc: Matthew Wilcox <matthew@wil.cx>,
Containers <containers@lists.linux-foundation.org>,
Jamie Lokier <jamie@shareable.org>,
linux-fsdevel@vger.kernel.org, Dan Smith <danms@us.ibm.com>,
Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [PATCH 0/5][v5][cr] Checkpoint/restart file locks
Date: Fri, 29 Oct 2010 11:35:07 -0700 [thread overview]
Message-ID: <20101029183507.GA6726@us.ibm.com> (raw)
In-Reply-To: <AANLkTiktKVuAtjPaHT9d+7ATpKn+jMonFYzeEmd85L3o@mail.gmail.com>
Lin Ming [lin@ming.vg] wrote:
| Hi,
|
| Which tree are these patches against?
|
| I can't apply them neither to Linus tree(18cb657c) nor
| vfs-2.6.git/for-linus branch(a4cdbd8b).
These apply to the checkpoint/restart tree:
git://git.ncl.cs.columbia.edu/pub/git/linux-cr.git
They need the checkpoint/restart infrastructure which is not in the main
line kernel yet. We have been using the [cr] prefix to identify these
patches, but will add a pointer to the above tree in the future.
Thanks,
Sukadev
prev parent reply other threads:[~2010-10-29 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 6:16 [PATCH 0/5][v5][cr] Checkpoint/restart file locks Sukadev Bhattiprolu
2010-10-29 6:16 ` [PATCH 1/5][v5][cr]: Move file_lock macros into linux/fs.h Sukadev Bhattiprolu
2010-10-29 6:16 ` [PATCH 2/5][v5][cr]: Define flock_set() Sukadev Bhattiprolu
2010-10-29 6:16 ` [PATCH 3/5][v5][cr]: Define flock64_set() Sukadev Bhattiprolu
2010-10-29 6:16 ` [PATCH 4/5][v5][cr]: Checkpoint/restore file-locks Sukadev Bhattiprolu
2010-10-29 6:16 ` [PATCH 5/5][v5][cr]: Document design of C/R of file-locks Sukadev Bhattiprolu
2010-10-29 14:31 ` [PATCH 0/5][v5][cr] Checkpoint/restart file locks Lin Ming
2010-10-29 18:35 ` Sukadev Bhattiprolu [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=20101029183507.GA6726@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=danms@us.ibm.com \
--cc=jamie@shareable.org \
--cc=lin@ming.vg \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=swhiteho@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).