From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] drbd 0.7 with recent kernels?
Date: Mon, 14 Aug 2006 18:35:36 +0200 [thread overview]
Message-ID: <20060814163536.GF7226@soda.linbit> (raw)
In-Reply-To: <20060814131554.GC15779@marowsky-bree.de>
/ 2006-08-14 15:15:54 +0200
\ Lars Marowsky-Bree:
> Hi,
>
> did anyone already rip out the devfs support from drbd 0.7 to make it
> compile with the latest kernels from upstream again, so I can avoid
> doing it myself? ;-)
"latest kernels" ...
well, we still compile against 2.6.17 as is.
I'm happy to rip it out in trunk completely.
but since we support even 2.4 kernels in drbd 0.7,
there you probably have to do it yourself, in case it is neccessary.
maybe you could just ifdef some empty defines in drbd_compat*.h ?
--
: Lars Ellenberg Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com :
next prev parent reply other threads:[~2006-08-14 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 13:15 [Drbd-dev] drbd 0.7 with recent kernels? Lars Marowsky-Bree
2006-08-14 16:35 ` Lars Ellenberg [this message]
2006-08-14 19:47 ` Lars Marowsky-Bree
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=20060814163536.GF7226@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.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