From: Grant Grundler <grundler@puffin.external.hp.com>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] TODO list
Date: Mon, 16 Jul 2001 10:48:55 -0600 [thread overview]
Message-ID: <200107161648.KAA20976@puffin.external.hp.com> (raw)
In-Reply-To: Message from Matthew Wilcox <willy@debian.org> of "Fri, 13 Jul 2001 20:10:08 BST." <20010713201008.Q3048@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
>
> Here's some things which need to get fixed, courtesy of Alan Cox:
>
> * Documentation/parisc/unwritten appears out of date
Here's what I have so far. I'll try to finish revivewing the rest
tonight (or tomorrow) and submit bugs for what doesn't get done by the end
of the week.
grant
sys_idle ./include/asm-parisc/unistd.h: return sys_idle();
sys_idle() is obsolete - remove it.
reboot_setup() arch/parisc/kernel/process.c - delete this function
machine_halt NOP. needs someone else to review.
machine_power_on obsolete - delete it
exit_thread NOP
flush_thread needs someone else to review
die
die_if_no_fixup Do we need to export either of these?
Don't think so. We have "die_if_kernel".
strlen_user #define strlen_user(str) lstrnlen_user(str, 0x7fffffffL)
Kind of klugy...is that ok?
do_check_pgt_cache NOP. needs someone else to review.
set_pte_phys orphaned? needs someone else to review.
ffz ./include/asm-parisc/bitops.h:extern __inline__ unsigned long ffz(unsigned long word)
I think "static __inline__" is meant...
check_bugs NOP. TBD.
I haven't looked at these yet:
csum_partial
csum_partial_copy
csum_partial_copy_generic
csum_partial_nocheck
csum_partial_copy_from_user
csum_tcpudp_nofold
csum_tcpudp_magic
sigaddset
sigdelset
get_cycles
prev parent reply other threads:[~2001-07-16 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 19:10 [parisc-linux] TODO list Matthew Wilcox
2001-07-14 20:53 ` Matthew Wilcox
2001-07-16 16:48 ` Grant Grundler [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=200107161648.KAA20976@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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