From: Daniel Walker <dwalker@codeaurora.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] fix for msm_sdcc MMC driver for 2.6.34-rc1
Date: Sat, 13 Mar 2010 11:57:48 -0800 [thread overview]
Message-ID: <1268510268.21952.294.camel@desktop> (raw)
In-Reply-To: <20100313075248.GK12554@elf.ucw.cz>
On Sat, 2010-03-13 at 08:52 +0100, Pavel Machek wrote:
> On Mon 2010-03-08 12:58:56, Daniel Walker wrote:
> > Just one small trivial fix.
> >
> > The following changes since commit 6b7b284958d47b77d06745b36bc7f36dab769d9b:
> > Linus Torvalds (1):
> > Linux 2.6.33-rc2
> >
> > are available in the git repository at:
> >
> > git://codeaurora.org/quic/kernel/dwalker/linux-msm.git msm-mmc_sdcc
> >
> > Roel Kluin (1):
> > msm_sdcc.c: missing brackets in msmsdcc_resume()
>
> Cool, 2.6.34-rc1 boots on HTC Dream, as did 2.6.33. Does this mean I
> should try to set up MMC, too? MMC worked in your -working-mmc tree in
> 2.6.33...
No it shouldn't work in mainline yet. I am planning to integrate it into
-next tho.. I need to bring in SMD, which we also have in staging. There
are two divergent SMD development lines which I need to find some
solution to. The staging version is one development line from Google,
the other one is from Qualcomm .. MMC has a similar problem.
Daniel
prev parent reply other threads:[~2010-03-13 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 20:58 [GIT PULL] fix for msm_sdcc MMC driver for 2.6.34-rc1 Daniel Walker
2010-03-13 7:52 ` Pavel Machek
2010-03-13 19:57 ` Daniel Walker [this message]
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=1268510268.21952.294.camel@desktop \
--to=dwalker@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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 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.