From: Randolph Chung <tausq@debian.org>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] 2.5 status
Date: Tue, 15 Oct 2002 13:51:16 -0700 [thread overview]
Message-ID: <20021015205116.GR5602@tausq.org> (raw)
In-Reply-To: <20021015211627.A15163@parcelfarce.linux.theplanet.co.uk>
> - Serial code not working for a 712 (willy)
> - the fix for do_fork needs checking
> - stifb doesn't compile
> - mux driver needs to be forward ported from 2.4 (rbrad)
> - merge 2.5.42
> - think the tcpdiag_cookie patch in our tree is now obsolete
> - need to get an official number for PDC_CONS or MUX (any problem with using
> the same number for both?) (rbrad)
> - send .text.init -> .init.text change to Linus (willy)
> - send tulip changes to jgarzik (grant)
> - figure out why we have genrtc 1.05 in our tree when linus has 1.06
> - do a better job of vmlinux{32,64}.lds
> - review diff vs 2.4 for additional changes
> - review diff vs 2.5 for changes which still need to be sent to Linus.
- show_trace()/show_stack() etc need to be implemented for parisc. right
now they are just empty stubs. i have some initial versions of these
that are probably not quite correct. will look into it some more.
- our PDC early debug console hacks need to be cleaned up somehow
- pci serial is broken still in 2.5.41, may be fixed in 2.5.42
- drivers/pci/setup-bus.c has a hppa-specific #ifdef right now to
prevent pci reinit from hpmc'ing the machine. this probably needs to
go upstream
> would these lists be more useful in html or would they just bitrot?
email's good.... :-) perhaps keep the list in cvs (so people can
add/remove items) and you can post it periodically.
thanks,
randolph
next prev parent reply other threads:[~2002-10-15 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 20:16 [parisc-linux] 2.5 status Matthew Wilcox
2002-10-15 20:51 ` Randolph Chung [this message]
2002-10-15 22:52 ` Carlos O'Donell
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=20021015205116.GR5602@tausq.org \
--to=tausq@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.