From: Tom Rix <tom@bumblecow.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Please pull u-boot-pxa/next
Date: Thu, 29 Apr 2010 11:31:41 -0500 [thread overview]
Message-ID: <4BD9B46D.1000702@bumblecow.com> (raw)
In-Reply-To: <201004291341.45378.marek.vasut@gmail.com>
Marek Vasut wrote:
> Tom, ok, one more time, I moved the fix Wolfgang requested to another branch.
> Please pull these changes then.
> Cheers
>
> The following changes since commit 3699c28e6d16b563629c285311a0ce62a2c4c5d0:
> Wolfgang Denk (1):
> Merge branch 'master' of git://git.denx.de/u-boot-video
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-pxa.git next
>
> Marek Vasut (4):
> PXA: PXAMMC: Drop different delays for PXA27X
> PXA: PXAMMC: Add Monahans support
The name of this patch changed
http://www.mail-archive.com/u-boot at lists.denx.de/msg29975.html
This is close but not the same patch.
> PXA: Add UP2OCR register bit definitions
http://www.mail-archive.com/u-boot at lists.denx.de/msg31137.html
This is close but not the same patch
> PXA: Add missing MDREFR bits
>
> arch/arm/include/asm/arch-pxa/pxa-regs.h | 25 +++++++++++++++++++++----
> drivers/mmc/pxa_mmc.c | 17 ++++++-----------
> 2 files changed, 27 insertions(+), 15 deletions(-)
>
>
It seems like there are two patches in this set that were
changed without being posted to the mailing list.
Please post all changes to mailing list.
Tom
next prev parent reply other threads:[~2010-04-29 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 11:41 [U-Boot] [GIT PULL] Please pull u-boot-pxa/next Marek Vasut
2010-04-29 16:31 ` Tom Rix [this message]
2010-04-29 18:28 ` Marek Vasut
2010-05-03 17:06 ` Marek Vasut
2010-05-03 22:21 ` Tom Rix
-- strict thread matches above, loose matches on Subject: below --
2010-04-21 15:08 Marek Vasut
2010-04-28 18:07 ` Marek Vasut
2010-04-29 1:13 ` Marek Vasut
2010-04-29 1:54 ` Marek Vasut
2010-04-29 4:37 ` Wolfgang Denk
2010-04-29 11:39 ` Marek Vasut
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=4BD9B46D.1000702@bumblecow.com \
--to=tom@bumblecow.com \
--cc=u-boot@lists.denx.de \
/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