All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: PowerPC dev list <linuxppc-dev@ozlabs.org>,
	Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] cpm: Describe multi-user ram in its own device node.
Date: Sat, 29 Sep 2007 10:49:17 +0400	[thread overview]
Message-ID: <20070929104917.1585737e@kernel.crashing.org> (raw)
In-Reply-To: <08C0C9CB-C958-4B95-81B8-D0677CBA4399@kernel.crashing.org>

Hello Kumar,

On Fri, 28 Sep 2007 18:53:38 -0500
Kumar Gala wrote:

> 
> On Sep 28, 2007, at 3:30 PM, Vitaly Bordug wrote:
> 
> > Kumar,
> >
> > Realizing this may suffer a bit from cleanest-dts flame war, but  
> > anyway I pretty much see a lot of
> > sense in getting this in during next merge window. Is this possible?
> 
> Probably, does QE have muram?  I can't keep these things straight.
> 

cpms have dpram, qe has muram. these two are the same stuff in fact. Or you are asking about have QE stuff utilize such a binding at the same pass? 
-- 
Sincerely, Vitaly

  reply	other threads:[~2007-09-29  6:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 19:06 [PATCH] cpm: Describe multi-user ram in its own device node Scott Wood
2007-09-28 20:06 ` Vitaly Bordug
2007-09-28 20:10   ` Scott Wood
2007-09-28 20:25     ` Vitaly Bordug
2007-09-28 20:30 ` Vitaly Bordug
2007-09-28 23:53   ` Kumar Gala
2007-09-29  6:49     ` Vitaly Bordug [this message]
2007-09-29 14:34       ` Kumar Gala
2007-10-01 16:10         ` Scott Wood
2007-10-02 14:43           ` Kumar Gala
2007-10-02 14:49             ` Timur Tabi
2007-10-02 15:49               ` Scott Wood
2007-10-02 15:51                 ` Timur Tabi
2007-10-02 15:51                   ` Scott Wood
2007-10-02 17:11                   ` Kumar Gala
2007-10-02 14:43 ` Kumar Gala

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=20070929104917.1585737e@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.