From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm-1.0.1-rc1 doesn't generate proper patch for linux-2.4.10-pre1
Date: Tue, 28 Aug 2001 14:53:02 -0500 [thread overview]
Message-ID: <20010828145302.A25358@sistina.com> (raw)
In-Reply-To: <20010828135726.A22794@beaver.iucha.org>; from florin@iucha.net on Tue, Aug 28, 2001 at 01:57:26PM -0500
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Tue, Aug 28, 2001 at 01:57:26PM -0500, Florin Iucha wrote:
> 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.
Yep, the comparison in select_fragements is wrong. We're workign on it.
Thanks.
--
AJ Lewis
Sistina Software Inc. Voice: 612-638-0500
1313 5th St SE, Suite 111 Fax: 612-638-0500
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
Computer Science: solving today's problems tomorrow.
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-08-28 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 18:57 [linux-lvm] lvm-1.0.1-rc1 doesn't generate proper patch for linux-2.4.10-pre1 Florin Iucha
2001-08-28 19:53 ` AJ Lewis [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=20010828145302.A25358@sistina.com \
--to=lewis@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