From: john moser <bluefoxicy@linux.net>
To: linux-kernel@vger.kernel.org
Subject: struct task_struct -> task_t
Date: Mon, 19 Jan 2004 14:17:57 -0800 (PST) [thread overview]
Message-ID: <20040119221757.411BB3958@sitemail.everyone.net> (raw)
It has come to my attention that in some places in the kernel, 'struct task_struct'
is used; and in others, 'task_t' is used. Also, 'task_t' is
'typedef struct task_struct task_t;'.
I made a small script to change around as much as I could so that everything uses
task_t, but all the forward declarations make it difficult. The script doesn't
work as-is, so it will take you a few tries to compile and remove duplicate
declarations of task_t. If anyone's interested in changing all of these to be
consistent, this is your starting point.
running this in the top level of the source tree should get you started:
for i in `find . -type f`; do echo $i; cat $i | \
sed -e "s/struct task_struct/task_t/g" | \
sed -e "s/^\s*task_t;/struct task_struct;\ntypedef struct task_struct task_t;/g" \
> /tmp/tmpkernel; \
cat /tmp/tmpkernel > $i; rm /tmp/tmpkernel; done; \
cat include/linux/sched.h | \
sed -e "s/typedef task_t task_t/typedef struct task_struct task_t/g" | \
sed -e "s/task_t {/struct task_struct {/g" > /tmp/tmpkernel; \
cat /tmp/tmpkernel > include/linux/sched.h; rm /tmp/tmpkernel
That should also switch the forward declarations of struct task_struct over to
'struct task_struct; typedef struct task_struct task_t;' pairs. This leaves a few
holes, as there are some places where the typedef occurs after one has already
occured, and so these need to be fixed.
I am only able to deal with i386, and there's a lot of stuff in the asm includes
that needs to be adjusted by hand after running the above script.
_____________________________________________________________
Linux.Net -->Open Source to everyone
Powered by Linare Corporation
http://www.linare.com/
next reply other threads:[~2004-01-19 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 22:17 john moser [this message]
2004-01-19 22:24 ` viro
2004-01-19 23:57 ` Martin Hicks
2004-01-20 23:50 Albert Cahalan
2004-01-21 10:05 ` J.A. Magallon
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=20040119221757.411BB3958@sitemail.everyone.net \
--to=bluefoxicy@linux.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®