From: Mike Snitzer <snitzer@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: jbrassow@redhat.com, agk@redhat.com, dm-devel@redhat.com,
linux-raid@vger.kernel.org
Subject: Re: [PATCH v3 0/8] dm-raid (raid456) target
Date: Wed, 5 Jan 2011 17:36:29 -0500 [thread overview]
Message-ID: <20110105223628.GA13164@redhat.com> (raw)
In-Reply-To: <20101221141443.5aea0b12@notabene.brown>
On Mon, Dec 20 2010 at 10:14pm -0500,
Neil Brown <neilb@suse.de> wrote:
> On Mon, 20 Dec 2010 21:37:37 -0500 Mike Snitzer <snitzer@redhat.com> wrote:
>
> > I reviewed all patches and adjusted patch headers in preparation for
> > inclusion in Alasdair's tree (upstream target being v2.6.38). The 2
> > md/bitmap changes can obviously go through Neil's MD tree if that is
> > preferred.
> >
> > - added Copyright to the top of dm-raid.c
> > - fixed drivers/md/Kconfig so that DM_RAID will select MD_RAID456
> > - removed unused 'conf' variable in raid_status()
> > - few misc style and whitespace changes
> >
> > Neil,
> > Hopefully you're comfortable with the authorship of most of these
> > patches still being attributed to you (despite Jon's changes to your
> > original patches).
> >
> > Please advise, thanks!
>
> I haven't had a chance to have a proper look yet, and I'm about to go on
> leave for a couple of weeks.
> I'm probably happy with the authorship remaining as-is, but I reserve the
> right to change my mind (about anything) once I've had a chance to have a
> proper look.
Hi Neil,
Please advise on how you'd like things to proceed with this initial 8
patch set. Ideally we'd get them in to linux-next now and ultimately
2.6.38 before the merge window closes.
Thanks,
Mike
next prev parent reply other threads:[~2011-01-05 22:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 2:37 [PATCH v3 0/8] dm-raid (raid456) target Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 1/8] md/bitmap: revert dm-dirty-log preparation Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 2/8] md/bitmap: use DIV_ROUND_UP in bitmap_init_from_disk Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 3/8] md/raid5: use sysfs_notify_dirent_safe to avoid NULL pointer Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 4/8] dm raid: skeleton raid456 target support Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 5/8] dm: introduce target callbacks and congestion callback Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 6/8] dm: per-target unplug callback support Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 7/8] dm raid: add iterate_devices and io_hints functions Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 8/8] dm raid: add suspend and resume functions Mike Snitzer
2010-12-21 3:14 ` [PATCH v3 0/8] dm-raid (raid456) target Neil Brown
2011-01-05 22:36 ` Mike Snitzer [this message]
2011-01-06 10:46 ` NeilBrown
2011-01-06 14:43 ` Jonathan Brassow
2011-01-10 0:37 ` NeilBrown
2011-01-10 20:14 ` Jonathan Brassow
2011-01-06 15:56 ` [dm-devel] " Phillip Susi
2011-01-06 17:37 ` Jonathan Brassow
2011-01-06 20:59 ` [dm-devel] " Jonathan Brassow
2011-01-06 21:01 ` Jonathan Brassow
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=20110105223628.GA13164@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jbrassow@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.