mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: Patrick Caulfield <caulfield@sistina.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] Re: [PATCH] lvm in 2.4.15.pre3
Date: Mon, 12 Nov 2001 18:13:51 +0200	[thread overview]
Message-ID: <20011112181351.D1504@niksula.cs.hut.fi> (raw)
In-Reply-To: <20011112130101.A11020@tykepenguin.com> <E163GzN-0005po-00@the-village.bc.nu> <20011112162337.J26218@niksula.cs.hut.fi> <20011112143432.B580@tykepenguin.com> <20011112175101.B1504@niksula.cs.hut.fi> <20011112160412.C580@tykepenguin.com>
In-Reply-To: <20011112160412.C580@tykepenguin.com>; from caulfield@sistina.com on Mon, Nov 12, 2001 at 04:04:12PM +0000

On Mon, Nov 12, 2001 at 04:04:12PM +0000, you [Patrick Caulfield] claimed:
> On Mon, Nov 12, 2001 at 05:51:01PM +0200, Ville Herva wrote:
> > On Mon, Nov 12, 2001 at 02:34:32PM +0000, you [Patrick Caulfield] claimed:
> > > On Mon, Nov 12, 2001 at 04:23:37PM +0200, Ville Herva wrote:
> > > > On Mon, Nov 12, 2001 at 01:19:01PM +0000, you [Alan Cox] claimed:
> > > > > > Please apply the following patch to LVM in 2.4.13pre3.
> > > > > > 
> > > > > > It looks like the LVM patch that came from Alan calls alloc/free_kiovec_sz
> > > ()
> > > > > > functions which only exist in his tree.
> > > > > 
> > > > > Just sent Linus the same thing 8)
> > > > 
> > > > Sorry if this is a FAQ, but I see the LVM in .15pre3 is 0.9.1beta2. Are there
> > > > plans to merge something newer like 1.0.1pre4? 
> > > 
> > > I think you've misread the patch:
> > > 
> > > lvm.h:#define LVM_RELEASE_NAME "1.0.1-rc4(ish)"
> > 
> > Ummh, maybe I'm doing something wrong, but my copy of 2.4.15pre3 says
> > 
> > less -N include/linux/lvm.h:
> >     67  #ifndef _LVM_H_INCLUDE
> >     68  #define _LVM_H_INCLUDE
> >     69
> >     70  #define _LVM_KERNEL_H_VERSION   "LVM 0.9.1_beta2 (18/01/2001)"
> >     71
> >     72  #include <linux/config.h>
> >     73  #include <linux/version.h>
> > 
> 
> > ./drivers/md/lvm-internal.h:#define _LVM_INTERNAL_H_VERSION "LVM"LVM_RELEASE_NAME" ("LVM_RELEASE_DATE")"
> > 
> > Does it generate the LVM_RELEASE_NAME dynamically on first build?
> 
> No it doesn't. 
> 
> I can only assume your patch hasn't applied correctly - look at the patch
> itself:
> 
> @@ -67,9 +73,11 @@
>  #ifndef _LVM_H_INCLUDE
>  #define _LVM_H_INCLUDE
>  
> -#define        _LVM_KERNEL_H_VERSION   "LVM 0.9.1_beta2 (18/01/2001)"
> +#define LVM_RELEASE_NAME "1.0.1-rc4(ish)"
> +#define LVM_RELEASE_DATE "03/10/2001"
> +
> +#define _LVM_KERNEL_H_VERSION   "LVM "LVM_RELEASE_NAME" ("LVM_RELEASE_DATE")"
>  
> -#include <linux/config.h>
>  #include <linux/version.h>

It must be that (I was using non-gnu patch(1)).

Sorry for the noise.

BTW: When was 1.0.1-rc4 merged to -ac / mainline? I missed that...


-- v --

v@iki.fi

      parent reply	other threads:[~2001-11-12 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 13:01 Patrick Caulfield
2001-11-12 13:19 ` Alan Cox
2001-11-12 14:23   ` Ville Herva
     [not found]     ` <20011112143432.B580@tykepenguin.com>
     [not found]       ` <20011112175101.B1504@niksula.cs.hut.fi>
     [not found]         ` <20011112160412.C580@tykepenguin.com>
2001-11-12 16:13           ` Ville Herva [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=20011112181351.D1504@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=caulfield@sistina.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®