From: "Jan Kiszka" <jan.kiszka@googlemail.com>
To: "Andrey Borzenkov" <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc-4.1.1/kernel 2.6.16.18 - miscompiled external module (old parameter not found)
Date: Sat, 27 May 2006 19:09:01 +0200 [thread overview]
Message-ID: <58d0dbf10605271009s2b709250k115f31ed13be3b68@mail.gmail.com> (raw)
In-Reply-To: <200605271206.34427.arvidjaar@mail.ru>
2006/5/27, Andrey Borzenkov <arvidjaar@mail.ru>:
> After recompilation with new compiler of wifi driver I got:
>
> wlags49_h1_cs: falsely claims to have parameter channel
> wlags49_h1_cs: falsely claims to have parameter channel
> wlags49_h1_cs: falsely claims to have parameter channel
> wlags49_h1_cs: falsely claims to have parameter channel
>
...
>
> The distribution is Mandriva with gcc-4.1.1-1mdk, stock 2.6.16.18.
I observed the same effect with different code on a suse 10.1 box
(gcc-4.1) against 2.6.16.16. Is this a wanted breakage?
At least this made me start porting the involved code to the new
parameter scheme (and develop a strategy for 2.4 compatibility -
module_param_array wrapping...).
Jan
prev parent reply other threads:[~2006-05-27 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 8:06 Andrey Borzenkov
2006-05-27 17:09 ` Jan Kiszka [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=58d0dbf10605271009s2b709250k115f31ed13be3b68@mail.gmail.com \
--to=jan.kiszka@googlemail.com \
--cc=arvidjaar@mail.ru \
--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®