From: "Boris B. Zhmurov" <bb@kernelpanic.ru>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: MTRR compile failure in git
Date: Wed, 23 Nov 2005 11:49:34 +0300 [thread overview]
Message-ID: <43842D1E.6070006@kernelpanic.ru> (raw)
In-Reply-To: <Pine.SOC.4.61.0511231037390.13524@math.ut.ee>
Hello, Meelis Roos.
On 23.11.2005 11:38 you said the following:
> CC arch/i386/kernel/cpu/mtrr/main.o
> arch/i386/kernel/cpu/mtrr/main.c: In function 'set_mtrr':
> arch/i386/kernel/cpu/mtrr/main.c:225: error: 'ipi_handler' undeclared
> (first use in this function)
> arch/i386/kernel/cpu/mtrr/main.c:225: error: (Each undeclared identifier
> is reported only oncearch/i386/kernel/cpu/mtrr/main.c:225: error: for
> each function it appears in.)
>
> x86 UP i686 (PIII)
Yep. That happens after that patch:
tree e7ba0f1bc8764c36859e2cfa9421bb1d86f2e7f4
parent b3a5225f31180322fd7d692fd4cf786702826b94
author Russell King <rmk+kernel@arm.linux.org.uk> Wed, 23 Nov 2005
06:38:04 -0800
committer David S. Miller <davem@davemloft.net> Wed, 23 Nov 2005
06:38:04 -0800
[NET]: Shut up warnings in net/core/flow.c
Not really a network problem, more a !SMP issue.
net/core/flow.c:295: warning: statement with no effect
flow.c:295: smp_call_function(flow_cache_flush_per_cpu, &info, 1, 0);
Fix this by converting the macro to an inline function, which
also increases the typechecking for !SMP builds.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
--
Boris B. Zhmurov
mailto: bb@kernelpanic.ru
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
prev parent reply other threads:[~2005-11-23 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 8:38 Meelis Roos
2005-11-23 8:49 ` Boris B. Zhmurov [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=43842D1E.6070006@kernelpanic.ru \
--to=bb@kernelpanic.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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®