linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Kevin Fry <kevin@carts.com>
Cc: linuxppc emb3dd3d list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: HZ to MHZ, 2.4.2 kernel / update on my progress
Date: Mon, 20 Aug 2001 16:19:05 -0400	[thread overview]
Message-ID: <3B8170B9.97299F47@mvista.com> (raw)
In-Reply-To: 3B816F4F.E3633B0C@carts.com


Kevin Fry wrote:

> Couldnt have done it w/o you guys either, thanks again

I wish they were all this easy :-).

By the way, I pushed a bunch of new stuff for 8260 into the
linuxppc_2_4_devel tree last night.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-20 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 19:16 HZ to MHZ, 2.4.2 kernel Kevin Fry
2001-08-20 20:13 ` HZ to MHZ, 2.4.2 kernel / update on my progress Kevin Fry
2001-08-20 20:19   ` Dan Malek [this message]
2001-08-21 16:56     ` Elan Feingold

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=3B8170B9.97299F47@mvista.com \
    --to=dan@mvista.com \
    --cc=kevin@carts.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).