From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] patman changes?
Date: Thu, 31 Jan 2013 13:39:15 -0500 [thread overview]
Message-ID: <510ABA53.2000206@ti.com> (raw)
In-Reply-To: <CAD=FV=XWbLtzSw=KAhYzUpJKmuooUGeA33jw59noXJ92joKcYg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/31/2013 01:32 PM, Doug Anderson wrote:
> Hi,
>
> I posted a bunch of patman changes a bit ago and they've all been
> acked by Simon. Any chance of them landing? They're all visible
> here <http://patchwork.ozlabs.org/bundle/dianders/patman/>
>
> ...I think some of the changes have lost their acks on patchwork
> (I forgot to include Simon's v1 ack on my v2 changes). I'm happy
> to repost with his acks if that helps.
With the caveat that I only just now gave it a 30sec skim, I can take
the bundle or a pull request from Simon from the x86 tree. Got a
preference Simon?
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRCrpSAAoJENk4IS6UOR1WCSoP/ig9Magz1m+IY3nx36vZidfO
jNQmt68a1G84neBBSaXzO0y9QaUsYJbKbKTlc6nBYs65l2dbMK8/rupkANFFpGw4
85XOeYyn0I2AJ0kLvvAnth55poXC615hFCqQj3ztaNf20ROOmlgcN/WNiKU2dPpd
gm6OU1CUNteNQhHw378gY6LvYxjLWlPvypNiqJ31fwMRbQssMxoX/CCLbBgSm5m6
vHJ9U16Tk7B1l0Cmj/GHqa/4TYLuzVLsg0QhaxscS53MYrWtuFQfajkKsnxn9iy2
/fOVVLYy9iI9G99VI7XszYkeGKiX5QnQXL1HzhoJAUM1Rjv0Wqfjlt2moTf2T2M9
d6jLrUA7NoY9seKLH7NCfM0Htw63FVDIjowWyMBR6y/bO9yd1fiJwppkAT9AspHN
zwgXpwCMx2djwpLrcIZb7yA18yHVHKfWf+cPhARZ/iLBFjSUZk7WmaxKvbqIe/72
SayTZmGcV3noJVnnBtyGNCg6Sluz5HZoiNKr75lgm2W5G7rHY1RSNTn06qG+MyG6
l1v+sSPBuE05DBKaT8ekqB5kDdEX/Y4IAfqcH+eOLDkJ/S6u+XqqKLIDEcUA+oV4
iYI7IglQPsQEu5QEaHCRa8oKSvEL4OJAPZYPIIGjt1xkxMPld2imTYNMxCykvPW+
EN8JOkGhVbqGwHtXSWOJ
=Bp9L
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-01-31 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 18:32 [U-Boot] patman changes? Doug Anderson
2013-01-31 18:39 ` Tom Rini [this message]
2013-01-31 23:18 ` Simon Glass
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=510ABA53.2000206@ti.com \
--to=trini@ti.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 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.