From: DaMouse <damouse@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: FASTCALL fixing?
Date: Sat, 18 Sep 2004 15:43:08 +0100 [thread overview]
Message-ID: <1a56ea3904091807437ce86616@mail.gmail.com> (raw)
In-Reply-To: <200409172223.i8HMNgNu004437@harpo.it.uu.se>
On Sat, 18 Sep 2004 00:23:42 +0200 (MEST), Mikael Pettersson
<mikpe@csd.uu.se> wrote:
> On Fri, 17 Sep 2004 18:38:46 +0100, DaMouse <damouse@gmail.com> wrote:
> > I get errors about the fastcall and type conflicts in 2.4.27
> >(yeah its old.. i know :) ) I was wondering what the politically
> >correct way of fixing these are? adding fastcall type to
> >kernel/sched.c or removing FASTCALL() around it in sched.h?
>
> gcc-3.4? Known issue. Fixed in 2.4.28-pre ages ago,
> as the LKML archives should have told you.
>
Yeah, sorry i didn't think to look in 2.4.28-pre, thanks :)
-DaMouse
--
I know I broke SOMETHING but its there fault for not fixing it before me
next prev parent reply other threads:[~2004-09-18 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 22:23 FASTCALL fixing? Mikael Pettersson
2004-09-18 14:43 ` DaMouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-17 17:38 DaMouse
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=1a56ea3904091807437ce86616@mail.gmail.com \
--to=damouse@gmail.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