From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How to create a device mapper patch?
Date: Fri Oct 24 05:31:01 2003 [thread overview]
Message-ID: <20031024123243.H848@sistina.com> (raw)
In-Reply-To: <200310231626.53632.wim@unetix.nl>; from wim@unetix.nl on Thu, Oct 23, 2003 at 04:26:53PM +0200
On Thu, Oct 23, 2003 at 04:26:53PM +0200, wim@unetix.nl wrote:
> Hello,
>
> I tried to find out to make a patch for my kernel , 2.4.22,
> but there seems to be no documentation available how
> to generate a device mapper kernel patch.
> From the INSTALL file:
> ---
> If your kernel does not already contain device-mapper, patch,
> configure and build a new kernel with it
> ----
> Now this is nice , but doesn't explain how to generate a patch
> for the kernel. The patches directory only contains patches
> for 2.4.20 en 21 so, how do I generate a patch for 2.4.22?
> Device mapper is version 1.00.05
Does patching this into 2.4.22 fail for you ?
>
> TIA
>
> WB
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2003-10-24 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 9:28 [linux-lvm] How to create a device mapper patch? wim
2003-10-23 14:05 ` Herbert Poetzl
2003-10-27 8:32 ` wim
2003-10-23 16:10 ` Herbert Poetzl
2003-10-24 5:31 ` Heinz J . Mauelshagen [this message]
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=20031024123243.H848@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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