From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] u-boot-mips/master
Date: Mon, 1 Feb 2016 20:58:51 -0500 [thread overview]
Message-ID: <20160202015851.GV25786@bill-the-cat> (raw)
In-Reply-To: <CACUy__Xzoq=gPDZrV0+e31KAaGZQDRTr91iSk-MNrii20y+iEA@mail.gmail.com>
On Mon, Feb 01, 2016 at 10:53:29PM +0100, Daniel Schwierzeck wrote:
> Hi Tom,
>
> please pull some small MIPS updates and the initial Microchip PIC32
> support. Thanks!
>
>
> The following changes since commit 8cdae1dacde7dbe74d53a8ac1a05761a53c4f191:
>
> video: Correct 'tor' typo in comment (2016-01-30 10:58:47 +0100)
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-mips.git master
>
> for you to fetch changes up to 7d514a7407756d96996960c2ae539a4b464c65bc:
>
> board: Enable ethernet, tftpboot support to pic32mzdask board.
> (2016-02-01 22:14:02 +0100)
>
Applied to u-boot/master, thanks!
--
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/20160201/b5a69b87/attachment.sig>
next prev parent reply other threads:[~2016-02-02 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACUy__WFTeXy=asRLzGjfxtbC+F1d-S-h_wKo2aVBGYqpGFjYA@mail.gmail.com>
2016-02-01 21:53 ` [U-Boot] [PULL] u-boot-mips/master Daniel Schwierzeck
2016-02-02 1:58 ` Tom Rini [this message]
2017-11-28 23:34 Daniel Schwierzeck
-- strict thread matches above, loose matches on Subject: below --
2018-01-26 12:45 Daniel Schwierzeck
2018-01-26 18:22 ` Tom Rini
2018-03-21 22:31 Daniel Schwierzeck
2018-03-22 12:23 ` Tom Rini
2018-06-01 19:24 Daniel Schwierzeck
2018-06-02 1:09 ` 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=20160202015851.GV25786@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