From: Ben Dooks <ben@fluff.org>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: Pierre Ossman <drzeus@drzeus.cx>, Vitaly Luban <vitaly@luban.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Tokyo Electron SDIO controller (Ellen) support
Date: Mon, 3 Dec 2007 14:39:26 +0000 [thread overview]
Message-ID: <20071203143926.GC7855@fluff.org.uk> (raw)
In-Reply-To: <20071203142207.GA28101@gate.crashing.org>
On Mon, Dec 03, 2007 at 08:22:07AM -0600, Matt Porter wrote:
> On Sat, Dec 01, 2007 at 09:50:10PM +0100, Pierre Ossman wrote:
> > As for the patch, it's a big NAK at this point. Vendors who can't be bothered to follow
> > the standard will have to wait for Ben's separation patches before they can be supported.
> > Then they can have some voodoo front-end to handle their mistakes instead of turning
> > sdhci.c into a collection of hacks and workarounds.
>
> What's the status of Ben's separation patches? I haven't seen a posting of those
> versus a recent kernel. I've got some SDHCI driver glue for the non-pci Arasan core
> running in an older kernel tree with those patches. It's just waiting for the separation
> patches to hit the mmc or mainline tree.
I need to go back and try and sort out the last of Pierre's last
comments, and update to the latest kernel version. I was waiting
for 2.6.24-rc4 to re-start the effort to try and ensure there are
fewer changes due to fixes.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2007-12-03 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 8:27 [PATCH] Tokyo Electron SDIO controller (Ellen) support Vitaly Luban
2007-12-01 20:50 ` Pierre Ossman
2007-12-03 14:22 ` Matt Porter
2007-12-03 14:39 ` Ben Dooks [this message]
2008-02-08 23:06 ` Pierre Ossman
2008-08-06 22:39 ` Pierre Ossman
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=20071203143926.GC7855@fluff.org.uk \
--to=ben@fluff.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.org \
--cc=vitaly@luban.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).