From: Philipp Reisner <philipp.reisner@linbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Lars Ellenberg <lars.ellenberg@linbit.com>,
Andrew Morton <akpm@linux-foundation.org>,
drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [Drbd-dev] [PATCH 00/16] drbd: a block device for HA clusters
Date: Fri, 24 Jul 2009 17:20:21 +0200 [thread overview]
Message-ID: <200907241720.22771.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20090722145917.055eddc1.sfr@canb.auug.org.au>
On Wednesday 22 July 2009 06:59:17 Stephen Rothwell wrote:
> Hi Lars,
>
> On Tue, 21 Jul 2009 20:51:56 +0200 Lars Ellenberg
<lars.ellenberg@linbit.com> wrote:
> > Stephen: expect an explicit linux-next merge request
> > within the next few days.
>
> OK, just to be clear your tree should be based on Linus' tree (or some
> other *stable*, non rebasing, tree - *not* linux-next).
>
Hi Stephen,
Please add git://git.drbd.org/linux-2.6-drbd.git to linux-next.
The tree was initially based on v2.6.30-rc1. Later 2.6.31-rc1 was
merged in.
I verified that it still merges with 2.6.31-rc4 without conflicts.
Thanks!
-Philipp
--
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com
DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2009-07-24 15:20 UTC|newest]
Thread overview: 23+ 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 ` [PATCH 00/16] drbd: a block device for HA clusters Andrew Morton
2009-07-21 18:51 ` [Drbd-dev] " Lars Ellenberg
2009-07-22 4:59 ` Stephen Rothwell
2009-07-24 15:20 ` Philipp Reisner [this message]
2009-07-26 23:24 ` Stephen Rothwell
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=200907241720.22771.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=akpm@linux-foundation.org \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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