From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] staging/dream: add missing include files/fix compilation
Date: Mon, 01 Mar 2010 13:15:18 -0800 [thread overview]
Message-ID: <1267478118.29769.16.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100301211057.GA3004@elf.ucw.cz>
On Mon, 2010-03-01 at 22:10 +0100, Pavel Machek wrote:
> How do I get that one? I tried killing the repository and redoing git
> pull, followed up by
You should just be able to do "git remotes update" , then checkout the
branch again.
> git checkout refs/remotes/origin/working-mmc
>
> only to get (git log): [I think I was there before].
>
> commit 2b0bcf161e83fc7d45476f3330f06b656a1f03d4
> Author: Daniel Walker <dwalker@codeaurora.org>
> Date: Mon Feb 22 12:29:17 2010 -0800
>
> DMA fixes (get MMC working).
>
> commit 5fc33446739aa7a0826d98a00cc50a712c6d60eb
> Author: San Mehat <san@google.com>
> Date: Wed Feb 3 12:59:29 2010 -0800
>
> drivers: mmc: msm_sdcc: Add EMBEDDED_SDIO support
>
> Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
I actually dropped a patch between the two above, otherwise the history
is very similar. I think you have the right one, are you still getting
the compile errors?
Daniel
next prev parent reply other threads:[~2010-03-01 21:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 20:59 [PATCH] staging/dream: add missing include files/fix compilation Pavel Machek
2010-01-15 0:24 ` Greg KH
2010-01-19 5:45 ` Pavel Machek
2010-01-19 15:14 ` Daniel Walker
2010-01-31 8:44 ` Pavel Machek
2010-01-31 9:28 ` Pavel Machek
2010-01-31 15:58 ` Daniel Walker
2010-02-25 19:30 ` Pavel Machek
2010-02-25 19:36 ` Daniel Walker
2010-02-25 19:41 ` Pavel Machek
2010-02-25 19:48 ` Daniel Walker
[not found] ` <20100226213107.GA29615@elf.ucw.cz>
[not found] ` <1267469856.29769.9.camel@c-dwalke-linux.qualcomm.com>
2010-03-01 21:10 ` Pavel Machek
2010-03-01 21:15 ` Daniel Walker [this message]
2010-03-01 21:41 ` Pavel Machek
2010-03-03 6:48 ` Pavel Machek
2010-01-31 13:31 ` Daniel Walker
2010-01-19 15:54 ` Greg KH
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=1267478118.29769.16.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).