linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: consistent_alloc() on 82xx
Date: Thu, 9 Jun 2005 14:05:36 -0400	[thread overview]
Message-ID: <606851a1e01a1d42846b10db51399f1e@embeddededge.com> (raw)
In-Reply-To: <42A7DE75.8040205@intracom.gr>


On Jun 9, 2005, at 2:15 AM, Pantelis Antoniou wrote:

> I may also need consistent_alloc for some testing reasons Dan. :)

No, you don't :-)

Thanks.


	-- Dan

  parent reply	other threads:[~2005-06-09 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  9:29 consistent_alloc() on 82xx Alex Zeffertt
2005-06-08 16:12 ` Dan Malek
2005-06-09  6:15   ` Pantelis Antoniou
2005-06-09  9:06     ` Alex Zeffertt
2005-06-09 18:05     ` Dan Malek [this message]
2005-06-09  9:04   ` Alex Zeffertt
2005-06-09 19:05     ` Dan Malek
2005-06-10 10:11       ` Alex Zeffertt

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=606851a1e01a1d42846b10db51399f1e@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=panto@intracom.gr \
    /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).