From: Andrew Morton <akpm@linux-foundation.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Ben Dooks <ben-linux@fluff.org>, linux-mmc@vger.kernel.org
Subject: Re: + sdhci-add-no-hi-speed-bit-quirk-support.patch added to -mm tree
Date: Tue, 10 Aug 2010 14:34:34 -0700 [thread overview]
Message-ID: <20100810143434.01bea685.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTik5ANblTvTGh-4f9IL7VW8iPmQtRiN0BIDWjFGc@mail.gmail.com>
On Fri, 11 Jun 2010 12:25:32 +0900
Kyungmin Park <kmpark@infradead.org> wrote:
> On Fri, Jun 11, 2010 at 9:42 AM, Ben Dooks <ben-linux@fluff.org> wrote:
> > On Thu, Jun 10, 2010 at 01:43:19PM -0700, akpm@linux-foundation.org wrote:
> >>
> >> The patch titled
> >> __ __ __SDHCI: add no hi-speed bit quirk support
> >> has been added to the -mm tree. __Its filename is
> >> __ __ __sdhci-add-no-hi-speed-bit-quirk-support.patch
> >>
> >> Before you just go and hit "reply", please:
> >> __ __a) Consider who else should be cc'ed
> >> __ __b) Prefer to cc a suitable mailing list as well
> >> __ __c) Ideally: find the original patch on the mailing list and do a
> >> __ __ __ reply-to-all to that, adding suitable additional cc's
> >>
> >> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> >>
> >> See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> >> out what to do about this
> >>
> >> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> >>
> >> ------------------------------------------------------
> >> Subject: SDHCI: add no hi-speed bit quirk support
> >> From: Kyungmin Park <kmpark@infradead.org>
> >>
> >> Some SDHCI controllers like s5pc110 don't have an HISPD bit in the HOSTCTL
> >> register.
> >
> > It would be nice for someone at Samsung to (a) explain the differences
> > from the base SDHCI spec for all their hardware (the databooks are often
> > vague in this area) and (b) for the information for the extra registers
> > this IP block has to be explained in more detail (and the platform code
> > checked for this too).
>
> I hope also.
Going back over this dicussion, I get the impression that nothing
really got resolved or finished. So it is far from clear that I should
send these:
s5pc110-sdhci-s3c-can-override-host-capabilities.patch
s5pc110-sdhci-s3c-support-on-s5pc110.patch
sdhci-add-no-hi-speed-bit-quirk-support.patch
upstream. Could we please revisit all of this ASAP?
Thanks.
next prev parent reply other threads:[~2010-08-10 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 20:43 + sdhci-add-no-hi-speed-bit-quirk-support.patch added to -mm tree akpm
2010-06-11 0:42 ` Ben Dooks
2010-06-11 3:25 ` Kyungmin Park
2010-08-10 21:34 ` Andrew Morton [this message]
2010-08-17 5:15 ` Kyungmin Park
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=20100810143434.01bea685.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=kmpark@infradead.org \
--cc=linux-mmc@vger.kernel.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