From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] LPC32xx changes
Date: Tue, 11 Aug 2015 13:41:39 -0400 [thread overview]
Message-ID: <20150811174139.GK25532@bill-the-cat> (raw)
In-Reply-To: <55CA2B91.5010101@mleia.com>
On Tue, Aug 11, 2015 at 08:06:25PM +0300, Vladimir Zapolskiy wrote:
> Hello Tom,
>
> today I've opened U-boot patchwork and found that almost all my recent
> changes sent to U-boot mailing list are assigned to you. Would it be
> possible for you to review/apply them?
>
> As for today the collective work on LPC32xx support is significantly
> impeded.
Yes, I've moved them over to myself with the plan to apply them soon.
Note that I like to wait a bit after last posting to ensure that
everyone that would chime in has chimed in so that last patch might not
get applied soon. Thanks again!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150811/0dbfbad5/attachment.sig>
next prev parent reply other threads:[~2015-08-11 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 17:06 [U-Boot] LPC32xx changes Vladimir Zapolskiy
2015-08-11 17:41 ` Tom Rini [this message]
2015-08-11 18:20 ` LEMIEUX, SYLVAIN
2015-08-11 19:17 ` Tom Rini
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=20150811174139.GK25532@bill-the-cat \
--to=trini@konsulko.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