From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Patch for an up-to-date script/patch-kernel
Date: Tue, 18 Aug 2009 22:59:10 +0200 [thread overview]
Message-ID: <200908182259.10699.philipp.reisner@linbit.com> (raw)
In-Reply-To: <479b87b70908160900ue855e71l8212d7f6936064c4@mail.gmail.com>
Am Sonntag, 16. August 2009 18:00:21 schrieb Guillaume Plessis:
> Hello DRBD-devs,
> I encountered problems building a DRBD 8.3.2 patch with a 2.6.30.4 kernel
> (missing lru_cache.h, drbd_vli.h, drbd_tracing.c and drbd_tracing.h).
>
> You'll find as attachement a patch that fixes the patch-building process by
> filling "include_linux" and "drbd_source" with the good values.
>
> I hope it will be useful.
>
> Keep up the good work.
>
Whow the second patch of this kind within a few days. I never expected
that people actually patch DRBD into their kernels...
I have applied it.
Other than that we aim to get DRBD merged to Linux upstream with the
2.6.32 release. You can track out integration work from here:
git://git.drbd.org/linux-2.6-drbd.git
-Phil
next prev parent reply other threads:[~2009-08-18 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 16:00 [Drbd-dev] Patch for an up-to-date script/patch-kernel Guillaume Plessis
2009-08-18 20:59 ` Philipp Reisner [this message]
2009-08-18 21:16 ` Guillaume Plessis
2009-08-18 21:24 ` Anthony.D'Ambrosio
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=200908182259.10699.philipp.reisner@linbit.com \
--to=philipp.reisner@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