From: Mike Snitzer <snitzer@redhat.com>
To: agk@redhat.com
Cc: dm-devel@redhat.com
Subject: [PATCH v2 0/4] dm log userspace: a fix and other improvements
Date: Fri, 3 Dec 2010 18:12:46 -0500 [thread overview]
Message-ID: <1291417970-5626-1-git-send-email-snitzer@redhat.com> (raw)
Alasdair,
I've reviewed all of these patches from Jon:
- cleaned up all patch headers and subjects a bit
- patch 1 is a fix that should go to 2.6.37
- the others are fine to go to linux-next (and queue for 2.6.38)
- made some changes to patch 3 (uninit 'type' warning, move 'group'
from end of 'log_c' structure to flush_by_group's stack). Jon may
clean up the flush_by_group() list processing further but I've added
a useful comment about the final list_splice_init.
Thanks,
Mike
Jonathan Brassow (4):
dm log userspace: trap all errors from failed log construction
dm log userspace: split flush queue
dm log userspace: group clear and mark requests
dm log userspace: add version number to communication structure
drivers/md/dm-log-userspace-base.c | 130 ++++++++++++++++++++++++++------
drivers/md/dm-log-userspace-transfer.c | 1 +
include/linux/dm-log-userspace.h | 13 +++-
3 files changed, 119 insertions(+), 25 deletions(-)
--
1.7.2.3
next reply other threads:[~2010-12-03 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 23:12 Mike Snitzer [this message]
2010-12-03 23:12 ` [PATCH v2 1/4] dm log userspace: trap all errors from failed log construction Mike Snitzer
2010-12-03 23:12 ` [PATCH v2 2/4] dm log userspace: split flush queue Mike Snitzer
2010-12-03 23:12 ` [PATCH v2 3/4] dm log userspace: group clear and mark requests Mike Snitzer
2010-12-03 23:12 ` [PATCH v2 4/4] dm log userspace: add version number to communication structure Mike Snitzer
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=1291417970-5626-1-git-send-email-snitzer@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@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).