From: Chris Ball <cjb@laptop.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: zhangfei gao <zhangfei.gao@gmail.com>,
linux-mmc@vger.kernel.org, Kyungmin Park <kmpark@infradead.org>,
eric.y.miao@gmail.com, Haojian Zhuang <haojian.zhuang@gmail.com>
Subject: Re: [PATCH] add support PXA168/PXA910/MMP2 SD Host Controller
Date: Tue, 21 Sep 2010 17:18:07 +0100 [thread overview]
Message-ID: <20100921161807.GA18231@void.printf.net> (raw)
In-Reply-To: <20100921101116.GE3168@pengutronix.de>
Hi Wolfram,
On Tue, Sep 21, 2010 at 12:11:16PM +0200, Wolfram Sang wrote:
> I guess to fully understand all constraints, one must really working
> with your platform, what I don't do. I agree that a nicely working
> driver is better than no driver; however, I fear once a driver hit the
> mainline being non-pltfm, it will hardly be converted later, even if it
> was considered to be worthwhile. So this is why I ask initially if it
> couldn't be done.
>
> Chris, do you see a rule of thumb here? Or what are your preferences?
I agree with you entirely: even if we end up deciding not to use -pltfm
here (which looks like it's probably going to be the case), we should at
least specify what's stopping us from doing so and look into extending
-pltfm so that it might be useful next time around. So, thank you for
asking those questions!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-09-21 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 9:46 [PATCH] add support PXA168/PXA910/MMP2 SD Host Controller zhangfei gao
2010-09-20 9:50 ` Wolfram Sang
2010-09-20 12:09 ` zhangfei gao
2010-09-20 13:10 ` Wolfram Sang
2010-09-21 8:24 ` zhangfei gao
2010-09-21 10:11 ` Wolfram Sang
2010-09-21 10:18 ` Eric Miao
2010-09-21 16:18 ` Chris Ball [this message]
2010-09-21 1:03 ` Chris Ball
2010-09-21 3:16 ` zhangfei gao
2010-09-22 2:27 ` Chris Ball
2010-09-21 9:42 ` claud yu
2010-09-26 9:05 ` zhangfei gao
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=20100921161807.GA18231@void.printf.net \
--to=cjb@laptop.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=kmpark@infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=w.sang@pengutronix.de \
--cc=zhangfei.gao@gmail.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.