From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org, Li Yang <leoli@freescale.com>
Subject: Re: [PATCH 4/11] qe_lib: Add QE I/O ports API
Date: Fri, 22 Sep 2006 09:22:01 +1000 [thread overview]
Message-ID: <1158880922.26347.134.camel@localhost.localdomain> (raw)
In-Reply-To: <20060921192137.5c6af005@vitb.ru.mvista.com>
> Well, eventually this stuff aims to serve not 83xx/qe, but for cpm(1,2)-equipped stuff
> too. Apparently, we'll have to do something wise to afford that...
>
> OTOH, this is good as a starting point I guess.
This is typical of stuff that should be in the device-tree
Ben.
next prev parent reply other threads:[~2006-09-21 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 14:52 [PATCH 4/11] qe_lib: Add QE I/O ports API Joakim Tjernlund
2006-09-21 15:21 ` Vitaly Bordug
2006-09-21 23:22 ` Benjamin Herrenschmidt [this message]
2006-09-22 6:29 ` Li Yang-r58472
2006-09-21 20:38 ` Andy Fleming
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 12:18 Li Yang
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=1158880922.26347.134.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=vbordug@ru.mvista.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 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).