linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@ppc.kernel.org>
To: Nicholas Olinsky <olinskyn@sunnyside.wednet.edu>
Cc: linuxppc-dev@lists.linuxppc.org,
	"David T. McWherter" <dtm@vramp.net>,
	linuxppc-ans-support@hellfire.dusers.drexel.edu
Subject: Re: ANS Patches en route to the 2.2.x kernel?
Date: Thu, 1 Apr 1999 17:07:25 -0700	[thread overview]
Message-ID: <19990401170725.A14891@persephone.ppc.kernel.org> (raw)
In-Reply-To: <3703D228.56E8AA58@sunnyside.wednet.edu>; from Nicholas Olinsky on Thu, Apr 01, 1999 at 12:08:11PM -0800


It won't be right away.  There are some other patches in the queue that I
need to sort through.  They will be coming in within a couple weeks.  We
have a lot of architectures now so patches are coming into the tree more
slowly.

} Now that the patches have been upload, when can we expect ANS support to be a
} part of the main kernel? Will LinuxPPC 5 support ANS without the hoop jumping
} we current go through?

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-04-02  0:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-23  2:17 ANS Patches en route to the 2.2.x kernel? Darron Froese
1999-03-23 23:49 ` David T. McWherter
1999-03-24  3:57 ` Cort Dougan
1999-03-25  4:32   ` David T. McWherter
1999-04-01 20:08     ` Nicholas Olinsky
1999-04-02  0:07       ` Cort Dougan [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=19990401170725.A14891@persephone.ppc.kernel.org \
    --to=cort@ppc.kernel.org \
    --cc=dtm@vramp.net \
    --cc=linuxppc-ans-support@hellfire.dusers.drexel.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olinskyn@sunnyside.wednet.edu \
    /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).