From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] LPC32XX / DevKit3250 support
Date: Tue, 06 Dec 2011 15:56:25 +0200 [thread overview]
Message-ID: <4EDE1F09.5000008@mleia.com> (raw)
Hi Albert,
I would like to ask you to upmerge NXP LPC32XX and DevKit3250 support.
I didn't receive any response from you and I can't detect, if something
is still missing, or you're willing to include the changes into the next
merge window.
I tend to think that there are no stoppers anymore in inclusion of the
SoC and board support, but please share your opinion.
Links in the Patchwork (the cover letter is absent there, though)
* http://patchwork.ozlabs.org/patch/125579/
* http://patchwork.ozlabs.org/patch/125577/
* http://patchwork.ozlabs.org/patch/125578/
--
With best wishes,
Vladimir
reply other threads:[~2011-12-06 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EDE1F09.5000008@mleia.com \
--to=vz@mleia.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