From: Ali Akcaagac <ali.akcaagac@stud.fh-wilhelmshaven.de>
To: linux-kernel@vger.kernel.org
Subject: Re: PATCH: gcc3.0.2 workaround for 8139too
Date: 25 Nov 2001 16:57:59 +0100 [thread overview]
Message-ID: <1006703880.5039.0.camel@ulixys> (raw)
In-Reply-To: <slrna02427.3v.reneb@orac.aais.org>
In-Reply-To: <1006394515.14661.0.camel@ulixys> <1006691124.320.0.camel@ulixys> <slrna02427.3v.reneb@orac.aais.org>
On Sun, 2001-11-25 at 16:37, Rene Blokland wrote:
> cd d*/n*
> sh ../../foo
> cd /linux
> make
> There you go!
ok, i haven't tested this and don't even know if this works here. i for
now belive that it will work but that error has a _reason_ to happen for
some unknown issues. i'd better go for a cleaner solution right now then
forcing some crashes that _may_ happen because of borked _assembly_ code
that may be generated..
what i am thinking now (and i may be wrong). let's say i compile it your
way everything will be fine no visible errors and so on. now i use that
driver. everything works but under certain circumstances it may jump
into that CASE and crash because the compilers wasn't able to create a
clean code for it.
at least it was a quick solution to solve my personal needs that i
wanted to share with others maybe people not so involved into fixing
stuff.
but thank you. i will try this one out as soon as i update my kernel :)
--
Name....: Ali Akcaagac
Status..: Student Of Computer & Economic Science
E-Mail..: mailto:ali.akcaagac@stud.fh-wilhelmshaven.de
WWW.....: http://www.fh-wilhelmshaven.de/~akcaagaa
next prev parent reply other threads:[~2001-11-25 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 2:01 PATCH: gcc3.0.2 workaround for 8139too Ali Akcaagac
2001-11-25 12:25 ` Ali Akcaagac
2001-11-25 15:37 ` Rene Blokland
2001-11-25 15:57 ` Ali Akcaagac [this message]
2001-11-26 8:58 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2001-11-26 8:11 Andris Pavenis
2001-11-26 14:45 Luben Tuikov
2001-11-26 14:56 ` Ali Akcaagac
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=1006703880.5039.0.camel@ulixys \
--to=ali.akcaagac@stud.fh-wilhelmshaven.de \
--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