From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, Trond.Myklebust@netapp.com,
torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-cachefs@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] Add wait_on_atomic_t() and wake_up_atomic_t() [ver #2]
Date: Fri, 10 May 2013 21:47:52 +0100 [thread overview]
Message-ID: <26063.1368218872@warthog.procyon.org.uk> (raw)
In-Reply-To: <20130510193307.3045.21609.stgit@warthog.procyon.org.uk>
Fengguang's kbuild bot found a compile error on one arch with this patch, so
I've pushed a new version to the git tree.
David
next prev parent reply other threads:[~2013-05-10 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 19:32 [PATCH 0/8] Fix assorted FS-Cache issues [ver #2] David Howells
2013-05-10 19:33 ` [PATCH 1/8] Add wait_on_atomic_t() and wake_up_atomic_t() " David Howells
2013-05-10 20:47 ` David Howells [this message]
2013-05-10 19:33 ` [PATCH 2/8] fs/fscache: remove spin_lock() from the condition in while() " David Howells
2013-05-10 19:33 ` [PATCH 3/8] CacheFiles: name i_mutex lock class explicitly " David Howells
2013-05-10 19:33 ` [PATCH 4/8] FS-Cache: Don't sleep in page release if __GFP_FS is not set " David Howells
2013-05-10 19:33 ` [PATCH 5/8] FS-Cache: Uninline fscache_object_init() " David Howells
2013-05-10 19:33 ` [PATCH 6/8] FS-Cache: Wrap checks on object state " David Howells
2013-05-10 19:33 ` [PATCH 7/8] FS-Cache: Fix object state machine to have separate work and wait states " David Howells
2013-05-10 19:34 ` [PATCH 8/8] FS-Cache: Simplify cookie retention for fscache_objects, fixing access problems " David Howells
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=26063.1368218872@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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