Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] 2.5 status
Date: Tue, 15 Oct 2002 18:52:14 -0400	[thread overview]
Message-ID: <20021015225214.GC26368@systemhalted> (raw)
In-Reply-To: <20021015211627.A15163@parcelfarce.linux.theplanet.co.uk>

> In an attempt to get more people involved in the 2.5 porting effort, I'm
> going to try to send out weekly updates of what's going on.  Feel free to
> respond to things and point out where I'm wrong.

Thanks Willy :)
 
>  - Serial code not working for a 712 (willy)
>  - the fix for do_fork needs checking
>  - stifb doesn't compile

Didn't Helge just fix this?

>  - 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

e.g. Things in 2.4 not in 2.5?

>  - review diff vs 2.5 for changes which still need to be sent to Linus.
> would these lists be more useful in html or would they just bitrot?

Sending things to the mailing list gets you both:
- HTML based ref. of list archives.
- Ever present reminder in my parisc-linux folder.

Here's to getting all of the PA changes into 2.5! :)

c.

      parent reply	other threads:[~2002-10-15 22:52 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
2002-10-15 22:52 ` Carlos O'Donell [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=20021015225214.GC26368@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --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