From: Arjan van de Ven <arjan@infradead.org>
To: Lars Ellenberg <lars.ellenberg@linbit.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
lmb@suse.de, jens.axboe@oracle.com, neilb@suse.de,
hch@infradead.org, James.Bottomley@suse.de,
linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com,
akpm@linux-foundation.org, bart.vanassche@gmail.com,
davej@redhat.com, gregkh@suse.de, kosaki.motohiro@jp.fujitsu.com,
kyle@moffetthome.net, torvalds@linux-foundation.org,
nab@linux-iscsi.org, knikanth@suse.de,
philipp.reisner@linbit.com, sam@ravnborg.org,
Mauelshagen@redhat.com
Subject: Re: [GIT PULL] DRBD for 2.6.32
Date: Mon, 21 Sep 2009 16:52:52 +0200 [thread overview]
Message-ID: <20090921165252.04e335b1@infradead.org> (raw)
In-Reply-To: <20090921144308.GG8072@barkeeper1-xen.linbit>
On Mon, 21 Sep 2009 16:43:08 +0200
Lars Ellenberg <lars.ellenberg@linbit.com> wrote:
> We can choose whatever user-kernel interface you like,
> and change it with every dot release --
> we'd just need to add additional compat code into
> the drbdsetup userland binary.
uh no.
the kernel<->userspace ABI is stable.
we don't go about randomly changing it
(extending it is fine obviously)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-09-21 14:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 14:45 [GIT PULL] DRBD for 2.6.32 Philipp Reisner
2009-09-15 23:19 ` Christoph Hellwig
2009-09-16 8:33 ` Philipp Reisner
2009-09-17 8:12 ` Lars Ellenberg
2009-09-17 16:02 ` James Bottomley
2009-09-17 16:11 ` Christoph Hellwig
2009-09-18 3:32 ` Neil Brown
2009-09-18 20:08 ` Jens Axboe
2009-09-19 5:14 ` FUJITA Tomonori
2009-09-19 22:02 ` Lars Marowsky-Bree
2009-09-19 23:56 ` Dan Williams
2009-09-21 13:39 ` FUJITA Tomonori
2009-09-21 14:43 ` Lars Ellenberg
2009-09-21 14:52 ` Arjan van de Ven [this message]
2009-09-21 16:53 ` Lars Ellenberg
2009-09-21 22:27 ` FUJITA Tomonori
2009-09-22 0:51 ` Kyle Moffett
2009-09-23 11:27 ` FUJITA Tomonori
2009-09-23 11:57 ` Christoph Hellwig
2009-09-23 14:01 ` Kyle Moffett
2009-09-23 23:21 ` FUJITA Tomonori
2009-09-22 6:20 ` Lars Marowsky-Bree
2009-09-23 11:36 ` FUJITA Tomonori
2009-09-23 23:06 ` Neil Brown
2009-09-23 23:37 ` FUJITA Tomonori
2009-09-25 5:27 ` Neil Brown
2009-09-25 9:59 ` Lars Marowsky-Bree
2009-09-21 14:55 ` [Drbd-dev] " Lars Ellenberg
2009-09-22 5:37 ` Heinz Mauelshagen
2009-09-17 8:50 ` Lars Marowsky-Bree
2009-09-16 0:46 ` KOSAKI Motohiro
2009-09-16 9:19 ` Philipp Reisner
2009-09-17 18:52 devzero
2009-09-23 19:10 devzero
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=20090921165252.04e335b1@infradead.org \
--to=arjan@infradead.org \
--cc=James.Bottomley@suse.de \
--cc=Mauelshagen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@gmail.com \
--cc=davej@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kyle@moffetthome.net \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@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 \
--cc=torvalds@linux-foundation.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 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.