From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Cc: Rusty Trivial Russell <trivial@rustcorp.com.au>
Subject: [PATCH] duplicate extern char _stext
Date: Sun, 5 Jan 2003 15:55:34 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.4.21.0301051553420.10519-100000@vervain.sonytel.be> (raw)
Kill duplicate extern char _stext (already declared globally 14 lines before)
--- linux-2.5.54/include/asm-i386/hw_irq.h.orig Thu Jan 2 12:55:06 2003
+++ linux-2.5.54/include/asm-i386/hw_irq.h Thu Jan 2 15:16:02 2003
@@ -76,7 +76,6 @@
{
unsigned long eip;
extern unsigned long prof_cpu_mask;
- extern char _stext;
#ifdef CONFIG_PROFILING
extern void x86_profile_hook(struct pt_regs *);
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2003-01-05 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.GSO.4.21.0301051553420.10519-100000@vervain.sonytel.be \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).