From: Kent Overstreet <koverstreet@google.com>
To: axboe@kernel.dk
Cc: linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org
Subject: pull request: bcache fixes
Date: Mon, 8 Apr 2013 13:42:46 -0700 [thread overview]
Message-ID: <20130408204246.GG15749@google.com> (raw)
Jens, here's the latest bcache fixes. All of it fairly minor:
The following changes since commit 169ef1cf6171d35550fef85645b83b960e241cff:
bcache: Don't export utility code, prefix with bch_ (2013-03-28 12:50:55 -0600)
are available in the git repository at:
http://evilpiepirate.org/git/linux-bcache.git bcache-for-upstream
for you to fetch changes up to cef5279735d3f6f0243e626963e6d5c84efade0a:
bcache: Disable broken btree fuzz tester (2013-04-08 13:33:49 -0700)
----------------------------------------------------------------
Geert Uytterhoeven (1):
bcache: Add missing #include <linux/prefetch.h>
Kent Overstreet (6):
bcache: Sparse fixes
bcache: Use WARN_ONCE() instead of __WARN()
bcache: Documentation updates
bcache: Fix a minor memory leak on device teardown
bcache: Fix a format string overflow
bcache: Disable broken btree fuzz tester
Documentation/bcache.txt | 88 ++++++++++++++++++++++
drivers/md/bcache/bset.c | 3 +-
drivers/md/bcache/btree.c | 3 +-
drivers/md/bcache/debug.c | 8 +-
drivers/md/bcache/journal.c | 2 +
drivers/md/bcache/super.c | 4 +-
drivers/md/bcache/util.c | 180 ++++++++++++++++++++++----------------------
7 files changed, 192 insertions(+), 96 deletions(-)
next reply other threads:[~2013-04-08 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 20:42 Kent Overstreet [this message]
[not found] ` <20130408204246.GG15749-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-04-09 7:15 ` pull request: bcache fixes Jens Axboe
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=20130408204246.GG15749@google.com \
--to=koverstreet@google.com \
--cc=axboe@kernel.dk \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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