From: Andrew Morton <akpm@linux-foundation.org>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
Greg KH <gregkh@suse.de>, Neil Brown <neilb@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Sam Ravnborg <sam@ravnborg.org>, Dave Jones <davej@redhat.com>,
Nikanth Karthikesan <knikanth@suse.de>,
"Lars Marowsky-Bree" <lmb@suse.de>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Kyle Moffett <kyle@moffetthome.net>,
Bart Van Assche <bart.vanassche@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
drbd-dev@lists.linbit.com,
Lars Ellenberg <lars.ellenberg@linbit.com>,
linux-next@vger.kernel.org
Subject: Re: [PATCH 00/16] drbd: a block device for HA clusters
Date: Mon, 20 Jul 2009 22:49:40 -0700 [thread overview]
Message-ID: <20090720224940.36da1ef8.akpm@linux-foundation.org> (raw)
In-Reply-To: <1246894775-10855-1-git-send-email-philipp.reisner@linbit.com>
On Mon, 6 Jul 2009 17:39:19 +0200 Philipp Reisner <philipp.reisner@linbit.com> wrote:
> As the first bit of the DBRD patch already got upstream (see commit
> 10fc89d01a) it is time to get more of DRBD towards mainline.
>
> Here is a post of drbd-8.3.2 for inclusion into linux-mm (or linux-next).
>
> Patch set attached. Git tree available:
> git pull git://git.drbd.org/linux-2.6-drbd.git drbd
I don't think I can be bothered reading all this again ;) I trust that
earlier review comments were suitably addressed.
Please prepare a tree for inclusion in linux-next, send that off to
Stephen and unless someone can identify reasons otherwise, send Linus a pull
request for 2.6.32-rc1.
next prev parent reply other threads:[~2009-07-21 5:51 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 15:39 [PATCH 00/16] drbd: a block device for HA clusters Philipp Reisner
2009-07-06 15:39 ` [PATCH 01/16] drbd: Entry in the MAINTAINERS file for DRBD Philipp Reisner
2009-07-06 15:39 ` [PATCH 02/16] lru_cache: track a fixed size cache of equal sized objects Philipp Reisner
2009-07-06 15:39 ` [PATCH 03/16] drbd: tracking of active extents Philipp Reisner
2009-07-06 15:39 ` [PATCH 04/16] drbd: dirty bitmap Philipp Reisner
2009-07-06 15:39 ` [PATCH 05/16] drbd: request state processing Philipp Reisner
2009-07-06 15:39 ` [PATCH 06/16] drbd: user space interface (based upon connector/netlink) Philipp Reisner
2009-07-06 15:39 ` [PATCH 07/16] drbd: internal data structures Philipp Reisner
2009-07-06 15:39 ` [PATCH 08/16] drbd: device state engine Philipp Reisner
2009-07-06 15:39 ` [PATCH 09/16] drbd: network IO threads Philipp Reisner
2009-07-06 15:39 ` [PATCH 10/16] drbd: the /proc/drbd interface Philipp Reisner
2009-07-06 15:39 ` [PATCH 11/16] drbd: worker thread Philipp Reisner
2009-07-06 15:39 ` [PATCH 12/16] drbd: variable length integer encoding Philipp Reisner
2009-07-06 15:39 ` [PATCH 13/16] drbd: String constants Philipp Reisner
2009-07-06 15:39 ` [PATCH 14/16] drbd: tracepoint probes Philipp Reisner
2009-07-06 15:39 ` [PATCH 15/16] drbd: documentation Philipp Reisner
2009-07-06 15:39 ` [PATCH 16/16] drbd: Kconfig and Makefile bits Philipp Reisner
2009-07-21 5:49 ` [PATCH 04/16] drbd: dirty bitmap Andrew Morton
2009-07-21 5:49 ` Andrew Morton [this message]
2009-07-21 18:51 ` [Drbd-dev] [PATCH 00/16] drbd: a block device for HA clusters Lars Ellenberg
2009-07-22 4:59 ` Stephen Rothwell
2009-07-24 15:20 ` Philipp Reisner
2009-07-26 23:24 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-05-15 12:10 [PATCH 00/16] DRBD: " Philipp Reisner
2009-05-14 22:31 devzero
2009-04-30 11:26 Philipp Reisner
2009-05-01 8:59 ` Andrew Morton
2009-05-01 11:15 ` Lars Marowsky-Bree
2009-05-01 13:14 ` Dave Jones
2009-05-01 19:14 ` Andrew Morton
2009-05-05 4:05 ` Christian Kujau
2009-05-02 7:33 ` Bart Van Assche
2009-05-03 5:36 ` Willy Tarreau
2009-05-03 5:40 ` david
2009-05-03 14:21 ` James Bottomley
2009-05-03 14:36 ` david
2009-05-03 14:45 ` James Bottomley
2009-05-03 14:56 ` david
2009-05-03 15:09 ` James Bottomley
2009-05-03 15:22 ` david
2009-05-03 15:38 ` James Bottomley
2009-05-03 15:48 ` david
2009-05-03 16:02 ` James Bottomley
2009-05-03 16:13 ` david
2009-05-04 8:28 ` Philipp Reisner
2009-05-04 17:24 ` James Bottomley
2009-05-05 8:21 ` Philipp Reisner
2009-05-05 14:09 ` James Bottomley
2009-05-05 15:56 ` Philipp Reisner
2009-05-05 17:05 ` James Bottomley
2009-05-05 21:45 ` Philipp Reisner
2009-05-05 21:53 ` James Bottomley
2009-05-06 8:17 ` Philipp Reisner
2009-05-05 15:03 ` Bart Van Assche
2009-05-05 15:57 ` Philipp Reisner
2009-05-05 17:38 ` Lars Marowsky-Bree
2009-05-03 10:06 ` Philipp Reisner
2009-05-03 10:15 ` Thomas Backlund
2009-05-03 5:53 ` Neil Brown
2009-05-03 6:24 ` david
2009-05-03 8:29 ` Lars Ellenberg
2009-05-03 11:00 ` Neil Brown
2009-05-03 21:32 ` Lars Ellenberg
2009-05-04 16:12 ` Lars Marowsky-Bree
2009-05-05 22:08 ` Lars Ellenberg
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=20090720224940.36da1ef8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bart.vanassche@gmail.com \
--cc=davej@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--cc=kyle@moffetthome.net \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lmb@suse.de \
--cc=nab@linux-iscsi.org \
--cc=neilb@suse.de \
--cc=philipp.reisner@linbit.com \
--cc=sam@ravnborg.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