From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: sdhci-devel@list.drzeus.cx, linux-kernel@vger.kernel.org
Subject: Re: [Sdhci-devel] PATCH: Fix 32bitism in SDHCI
Date: Thu, 15 Jun 2006 22:51:40 +0100 [thread overview]
Message-ID: <1150408300.3490.154.camel@localhost.localdomain> (raw)
In-Reply-To: <4491ABF7.4090204@drzeus.cx>
Ar Iau, 2006-06-15 am 20:50 +0200, ysgrifennodd Pierre Ossman:
> Yes and no. It's for a code path that's never supposed to be hit (and
> isn't except for hardware so broken it doesn't work anyway).
Oh I see, I didn't realise it was just for the obscure corner case
next prev parent reply other threads:[~2006-06-15 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 15:33 PATCH: Fix 32bitism in SDHCI Alan Cox
2006-06-15 16:59 ` [Sdhci-devel] " Pierre Ossman
2006-06-15 17:04 ` Russell King
2006-06-15 17:07 ` Pierre Ossman
2006-06-15 17:37 ` Alan Cox
2006-06-15 18:35 ` Mark Lord
2006-06-15 18:50 ` Pierre Ossman
2006-06-15 21:51 ` Alan Cox [this message]
2006-06-15 18:52 ` Russell King
2006-06-15 18:59 ` Daniel Drake
2006-06-15 19:05 ` 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=1150408300.3490.154.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=sdhci-devel@list.drzeus.cx \
/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