From: "Takeo Saito" <kernel@tranda.com.tw>
To: <fdavis@si.rr.com>, <linux-kernel@vger.kernel.org>
Cc: <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.9-ac18: __cpu_raise_softirq constantly redefined
Date: Sun, 30 Sep 2001 14:50:06 +0800 [thread overview]
Message-ID: <001e01c1497c$24934c50$b9c3fea9@w2ktakeon2> (raw)
In-Reply-To: <3BB6933A.5010905@si.rr.com>
Hello,
You can remove this define on interrupt.h,
because the define on ac-17 is bellow:
-----------------------------------------------------------------------
#ifndef __cpu_raise_softirq
#define __cpu_raise_softirq(cpu, nr) \
do { softirq_pending(cpu) |= 1UL << (nr); } while (0)
#endif
-----------------------------------------------------------------------
but on ac-18 is bellow:
-----------------------------------------------------------------------
#define __cpu_raise_softirq(cpu, nr) do { softirq_pending(cpu) |= 1UL <<
(nr); } while (0)
-----------------------------------------------------------------------
Best Regrads,
---
Takeo Tung (Takeo Saito)
----- Original Message -----
From: "Frank Davis" <fdavis@si.rr.com>
To: <linux-kernel@vger.kernel.org>
Cc: <alan@lxorguk.ukuu.org.uk>
Sent: Sunday, September 30, 2001 11:36 AM
Subject: 2.4.9-ac18: __cpu_raise_softirq constantly redefined
> Hello,
> While building 2.4.9-ac18, I constantly received the warning that '
> __cpu_raise_softirq redefined'. I didn't notice the warning while
> building 2.4.9-ac17.
>
> gcc version 2.91.66
>
> Regards,
> Frank
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2001-09-30 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-30 3:36 Frank Davis
2001-09-30 6:50 ` Takeo Saito [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='001e01c1497c$24934c50$b9c3fea9@w2ktakeon2' \
--to=kernel@tranda.com.tw \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fdavis@si.rr.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
all inboxes | Powered by JetHome®