Linux LVM users
 help / color / mirror / Atom feed
From: "Florin Iucha" <florin@iucha.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] lvm-1.0.1-rc1 doesn't generate proper patch for linux-2.4.10-pre1
Date: Tue, 28 Aug 2001 13:57:26 -0500	[thread overview]
Message-ID: <20010828135726.A22794@beaver.iucha.org> (raw)

Hello,

There is a problem with generating the lvm-1.0.1-rc1 patch for kernel
2.4.10-pre1. 

The patched kernel will not compile because of the
   get_hardsect_size/get_hardblocksize problem that occured in the transition
from 2.4.2 to 2.4.3.

Thinking about it a little, it looks like the patching mechanism got confused
about the kernel version and generated a patch for 2.4.1 . I am not sure about
this and I have not investigated it, but it smells like it.

Please look into it.

florin

-- 

"If it's not broken, let's fix it till it is."

41A9 2BDE 8E11 F1C5 87A6  03EE 34B3 E075 3B90 DFE4

             reply	other threads:[~2001-08-28 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28 18:57 Florin Iucha [this message]
2001-08-28 19:53 ` [linux-lvm] lvm-1.0.1-rc1 doesn't generate proper patch for linux-2.4.10-pre1 AJ Lewis

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=20010828135726.A22794@beaver.iucha.org \
    --to=florin@iucha.net \
    --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