From: Phil Howard <phil-linux-kernel@ipal.net>
To: linux-kernel@vger.kernel.org
Subject: what file to put a particular function in?
Date: Thu, 27 Dec 2001 07:07:14 -0600 [thread overview]
Message-ID: <20011227070714.A23383@vega.ipal.net> (raw)
In 2.4.17, the show_trace_task() function for sparc32 finally showed up.
The problem was, it was moved from traps.c to process.c. The confusion
is that in other platforms it is in traps.c, not process.c. DaveM
mentions in past posting that this is arbitrary. My question is, just
what is the scope of such arbitrary decisions? And is there even any
need to keep traps.c and process.c separate if functions can be freely
traded between them?
There is inconsistency. At least show_trace_task() shows up in some
platforms in one file, and in other platforms in another. This differs
even in related platforms like sparc32 (it's in process.c) and sparc64
(it's in traps.c). I believe there needs to be some kind of uniform
consistency between platforms where possible. Unless some special
constraint exists in a platform, I believe any function should show up
in the same place relative to the specific asm- tree.
I'm sure such changes really would not be wise for the remaining 2.4
sequence. But what about 2.5? Could this not be included as a goal in
the 2.5 tree, to get functions located more consistently?
--
-----------------------------------------------------------------
| Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ |
| phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/ |
-----------------------------------------------------------------
reply other threads:[~2001-12-27 13:07 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=20011227070714.A23383@vega.ipal.net \
--to=phil-linux-kernel@ipal.net \
--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®