From: Keith Owens <kaos@ocs.com.au>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.21-pre5 kksymoops for i386/ia64
Date: Thu, 20 Mar 2003 10:38:55 +1100 [thread overview]
Message-ID: <24872.1048117135@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 19 Mar 2003 16:39:39 BST." <20030319153939.GA30899@averell>
On Wed, 19 Mar 2003 16:39:39 +0100,
Andi Kleen <ak@muc.de> wrote:
>At least for me not working in cross compile setups is a critical bug.
>YMMV.
I can make modutils 2.4 (including kallsyms and depmod) work in cross
compile mode and still maintain backwards compatibility. Conceptually
the change is simple, but it affects a lot of code and needs a lot of
testing. I am not going to spend any time on adding cross compile
ability to modutils 2.4 until I see a defined need for it, people
saying "would be nice to have does not count". If I cannot get
kallsyms into the kernel for native compiles, why should I waste my
time making kallsyms work for the even smaller group of people who do
cross compiles?
Bottom line - when, and only when, the kksymoops patch is in the 2.4
kernel, then I will spend the time to make modutils 2.4 work in cross
compile mode. If you insist that kallsyms work in cross compile mode
before the patch goes in, then it is not going to happen and nobody
gets automatic oops decoding in 2.4.
next prev parent reply other threads:[~2003-03-19 23:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26040.1047888163@kao2.melbourne.sgi.com.suse.lists.linux.kernel>
2003-03-17 16:33 ` Andi Kleen
2003-03-17 23:41 ` Keith Owens
2003-03-18 2:18 ` Keith Owens
2003-03-19 15:39 ` Andi Kleen
2003-03-19 22:17 ` Keith Owens
2003-03-19 22:34 ` Andi Kleen
2003-03-19 23:38 ` Keith Owens [this message]
2003-03-26 14:24 ` David Woodhouse
2003-03-17 8:02 Keith Owens
2003-03-17 15:20 ` David Woodhouse
2003-03-18 0:29 ` Keith Owens
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=24872.1048117135@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=ak@muc.de \
--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®