From: Andrew Morton <akpm@digeo.com>
To: Wiktor Wodecki <wodecki@gmx.de>
Cc: linux-lvm@sistina.com
Subject: [linux-lvm] Re: 2.5.73-mm2
Date: Sun Jun 29 00:30:02 2003 [thread overview]
Message-ID: <20030628222938.78c16450.akpm@digeo.com> (raw)
In-Reply-To: <20030628115033.GA660@gmx.de>
Wiktor Wodecki <wodecki@gmx.de> wrote:
>
> On Fri, Jun 27, 2003 at 08:21:30PM -0700, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.73/2.5.73-mm2/
> >
> > Just bits and pieces.
>
> I have problems with lvm2 and the 2.5.73-mm2 patchset.
Could be because -mm uses a 64-bit dev_t.
Could you please revert
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.73/2.5.73-mm2/broken-out/64-bit-dev_t-kdev_t.patch
and retest?
I think there's a version of devicemapper userspace which works correctly
with 64-bit dev_t. Perhaps the Sistina team can shed some light.
next prev parent reply other threads:[~2003-06-29 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030627202130.066c183b.akpm@digeo.com>
2003-06-30 9:51 ` [linux-lvm] Re: 2.5.73-mm2 Wiktor Wodecki
2003-06-29 0:30 ` Andrew Morton [this message]
2003-06-30 9:51 ` Wiktor Wodecki
2003-06-30 10:23 ` Joe Thornber
2003-06-30 10:41 ` Wiktor Wodecki
2003-06-30 11:41 ` Heinz J . Mauelshagen
2003-06-30 12:29 ` Christophe Saout
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=20030628222938.78c16450.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-lvm@sistina.com \
--cc=wodecki@gmx.de \
/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