From: Kevin Corry <kevcorry@us.ibm.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] dm kernel patch size
Date: Tue, 6 Jul 2004 17:01:22 -0500 [thread overview]
Message-ID: <200407061701.22476.kevcorry@us.ibm.com> (raw)
In-Reply-To: <20040706214428.GW11597@polop.usc.edu>
On Tuesday 06 July 2004 4:44 pm, Garrick Staples wrote:
> On Tue, Jul 06, 2004 at 10:17:38PM +0100, Alasdair G Kergon alleged:
> > On Tue, Jul 06, 2004 at 01:56:23PM -0700, Garrick Staples wrote:
> > > Do the dm targets require the mm patchset? Is it possible to get
> > > _just_ the new dm targets?
> >
> > Yes - instead of applying the entire included -mm patch, take the dm
> > patches from the "broken out" version on his website:
> >
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/
> >
> > [Or work from Linus's bk tree, if you just want snapshot and pvmove.]
>
> The only dm-related patch in 2.6.7-mm6 that I can see is the new IO barrier
> patch.
It's all part of the "linus.patch", which is most likely a recent -bk patch.
> I don't want to follow any development trees, including Linus'. Can I get
> just the dm targets for 2.6.7 vanilla kernel.org?
You might be able to patch a temporary 2.6.7 kernel with 2.6.7-udm1, and then
copy over the contents of drivers/md/ to your non-mm tree. I don't *think*
there are any affected files outside of drivers/md/ (maybe
include/linux/device-mapper.h and dm-ioctl.h), but don't quote me on that. :)
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
prev parent reply other threads:[~2004-07-06 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 19:15 [linux-lvm] dm kernel patch size Garrick Staples
2004-07-06 20:46 ` Dan Merillat
2004-07-06 20:56 ` Garrick Staples
2004-07-06 21:17 ` Alasdair G Kergon
2004-07-06 21:44 ` Garrick Staples
2004-07-06 22:01 ` Kevin Corry [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=200407061701.22476.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=linux-lvm@redhat.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 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.