From: Kumar Gala <galak@kernel.crashing.org>
To: Kim Phillips <Kim.Phillips@freescale.com>, Li Yang <leoli@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: RFC: qe lib code location?
Date: Tue, 3 Oct 2006 11:34:11 -0500 [thread overview]
Message-ID: <724D42AC-3DBA-4B32-8E4A-914441251470@kernel.crashing.org> (raw)
I was wondering what peoples thought were on having the qe lib code
live in drivers/qe instead of sysdev/qe_lib (with the exception of
the interrupt controller code)
Yes, one can argue the cpm code should live in drivers/cpm by this
logic, but lets considered them grandfathered for now.
- kumar
next reply other threads:[~2006-10-03 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 16:34 Kumar Gala [this message]
2006-10-03 17:30 ` RFC: qe lib code location? Dan Malek
2006-10-16 18:46 ` Andy Fleming
2006-10-16 19:21 ` Dan Malek
2006-10-03 18:30 ` 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=724D42AC-3DBA-4B32-8E4A-914441251470@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Kim.Phillips@freescale.com \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.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