From: "Li Yang" <LeoLi@freescale.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 0/12] Add support for QE and 8360EMDS board -v2
Date: Fri, 29 Sep 2006 00:09:14 +0800 [thread overview]
Message-ID: <a0bc9bf80609280909r13e9ea31ldf0630969416cbff@mail.gmail.com> (raw)
In-Reply-To: <7178D84E-0290-4D3E-905E-C26C9908F40E@kernel.crashing.org>
On 9/28/06, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Sep 28, 2006, at 3:18 AM, Li Yang wrote:
>
> > Paul,
> >
> > The series of patches add generic QE infrastructure called
> > qe_lib, and MPC8360EMDS board support. Qe_lib is used by
> > QE device drivers such as ucc_geth driver.
> >
> > This version updates QE interrupt controller to use new irq
> > mapping mechanism, addresses all the comments received with
> > last submission and includes some style fixes.
> >
> > v2 change: Change to use device tree for BCSR and MURAM;
> > Remove I/O port interrupt handling code as it is not generic
> > enough.
>
> Before accepting any of this code, I'd like to see what the drivers
> look like that are using it. Its hard to make significant comments w/
> o seeing what the consumers of all the 'lib' code look like.
Current in-tree user of the lib is driver/net/ucc_geth.c. There is
also QE ATM driver which is included in Alex's 8360sar project. QE
USB host/client drivers are in Freescale LTIB BSP.
- Leo
next prev parent reply other threads:[~2006-09-28 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 8:18 [PATCH 0/12] Add support for QE and 8360EMDS board -v2 Li Yang
2006-09-28 15:54 ` Kumar Gala
2006-09-28 16:09 ` Li Yang [this message]
2006-09-28 16:37 ` Kumar Gala
2006-09-29 3:21 ` Li Yang-r58472
2006-09-29 12:41 ` Vitaly Bordug
2006-09-29 13:51 ` Kumar Gala
2006-09-29 14:28 ` Li Yang
2006-09-28 16:41 ` Vitaly Bordug
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=a0bc9bf80609280909r13e9ea31ldf0630969416cbff@mail.gmail.com \
--to=leoli@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).