From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [BUG?] register_blkdev: failed to get major for device mapper
Date: Tue, 20 Feb 2007 08:24:01 +0100 [thread overview]
Message-ID: <200702200824.06728.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <20070219115952.a06be52c.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Am Montag, 19. Februar 2007 schrieben Sie:
> On Mon, 19 Feb 2007 15:39:38 +0100 Rolf Eike Beer <eike-kernel@sf-tec.de>
wrote:
> > > It's totally weird. It prints the "skipped" message for every (!)
> > > number, not just for the blacklisted ones. And I've triple checked that
> > > I don't have missed the '{'.
> > >
> > > Compiler is SuSEs 4.1.0 from their 10.1. I remember some rumors that
> > > this thing is just broken?
> >
> > Ok, I'm using the compiler from SuSE 10.2 now and it works. Time that we
> > refuse to build if it's a 4.1.0.
>
> argh, I was down to suspecting gcc.
>
> I suppose we can just stir the code around to make it go away. Like this?
Too late, sorry. I've upgraded to 4.1.3 and it works fine now. Maybe I'll find
time to check again but this will take some days.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-02-20 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 13:37 [BUG?] register_blkdev: failed to get major for device mapper Rolf Eike Beer
2007-02-16 16:16 ` Dan Smith
2007-02-17 0:09 ` Andrew Morton
2007-02-19 10:01 ` Rolf Eike Beer
2007-02-19 10:29 ` Andrew Morton
2007-02-19 12:40 ` Rolf Eike Beer
2007-02-19 14:39 ` Rolf Eike Beer
2007-02-19 19:59 ` Andrew Morton
2007-02-20 7:24 ` Rolf Eike Beer [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=200702200824.06728.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.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