From: Christoph Hellwig <hch@infradead.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i386 entry.S problems
Date: Mon, 27 Sep 2004 10:00:18 +0100 [thread overview]
Message-ID: <20040927100018.A22468@infradead.org> (raw)
In-Reply-To: <s157d11c.077@emea1-mh.id2.novell.com>; from JBeulich@novell.com on Mon, Sep 27, 2004 at 09:37:10AM +0200
On Mon, Sep 27, 2004 at 09:37:10AM +0200, Jan Beulich wrote:
> >>> Christoph Hellwig <hch@infradead.org> 24.09.04 21:12:51 >>>
> >> +#if !defined(CONFIG_REGPARM) || __GNUC__ < 3
> >> pushl %ebp
> >> +#endif
> >
> >CONFIG_REGPARM n eeds gcc 3.0 or later
>
> Not sure what you try to point out here: the additions account for
> exactly that.
No, the || __GNUC__ < 3 is superflous. if CONFIG_REGPARM is defined
and __GNUC__ < 3 you have problems elsewhere already.
next parent reply other threads:[~2004-09-27 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s157d11c.077@emea1-mh.id2.novell.com>
2004-09-27 9:00 ` Christoph Hellwig [this message]
2004-09-27 11:19 i386 entry.S problems Jan Beulich
[not found] <2J0sK-6Ot-5@gated-at.bofh.it>
2004-09-27 10:58 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 9:50 Jan Beulich
2004-09-27 7:40 Jan Beulich
2004-09-27 7:37 Jan Beulich
[not found] <2HZ5Q-3MU-17@gated-at.bofh.it>
[not found] ` <2HZSa-4nZ-63@gated-at.bofh.it>
[not found] ` <2IFew-HK-9@gated-at.bofh.it>
2004-09-26 11:38 ` Andi Kleen
2004-09-24 15:25 Jan Beulich
2004-09-24 14:12 Jan Beulich
2004-09-24 14:57 ` Arjan van de Ven
2004-09-24 15:36 ` Alan Cox
2004-09-26 11:13 ` Ingo Molnar
2004-09-24 19:12 ` Christoph Hellwig
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=20040927100018.A22468@infradead.org \
--to=hch@infradead.org \
--cc=JBeulich@novell.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