Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Merge status update
Date: Tue, 17 Aug 2004 23:21:00 -0600	[thread overview]
Message-ID: <20040818052100.GA4924@colo.lackof.org> (raw)
In-Reply-To: <20040814210807.GX12936@parcelfarce.linux.theplanet.co.uk>

On Sat, Aug 14, 2004 at 10:08:07PM +0100, Matthew Wilcox wrote:
> The remainder:
> -rw-r--r--    1 willy    willy       20803 Aug 14 14:58 one.diff
> is composed of:
...
>  - tulip MII changes that someone needs to engage jgarzik in
>    bare-knuckle boxing over.

akpm (Andrew Morton) said I should send those to him.
My plan was to refresh the two sets of changes I have for tulip that
jgarzik hasn't accepted (because of udelay() calls). Then send those
to akpm + linux-net + jgarzik and ask innocently if there is
a better way to do the udelay() (someone suggested msleep() might be
an option).

> So a lot of minor stuff, but it's still not possible to build parisc
> out of Linus' tree ;-(

Well, don't despair. We really are not that far off.
Just need more time to work on it. I'm starting to feel a need for
another 3month unpaid leave of absence...maybe next summer...

grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-08-18  5:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14 21:08 [parisc-linux] Merge status update Matthew Wilcox
2004-08-18  5:21 ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-29 19:10 Kyle McMartin
2005-10-29 20:36 ` Matthew Wilcox

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=20040818052100.GA4924@colo.lackof.org \
    --to=grundler@parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox