All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] u-boot-mips/master
Date: Thu, 10 Mar 2016 11:01:11 -0500	[thread overview]
Message-ID: <20160310160111.GT23166@bill-the-cat> (raw)
In-Reply-To: <56E0028F.7020805@gmail.com>

On Wed, Mar 09, 2016 at 12:01:35PM +0100, Daniel Schwierzeck wrote:

> Hi Tom,
> 
> two fixes for MIPS:
> - fix a build error on Travis CI for pic32mzdask board
> - fix cache op for toolchains not supporting __builtin_mips_cache()
> 
> please consider pulling, thanks
> 
> 
> The following changes since commit deff6fb3a7790e93264292982000275e78bb12e5:
> 
>   malloc: remove !gd handling (2016-03-08 15:01:47 -0500)
> 
> are available in the git repository at:
> 
>   git://git.denx.de/u-boot-mips.git master
> 
> for you to fetch changes up to 40a09be2e925e6e4b56a236fec5aed2c002e9d6f:
> 
>   MIPS: pic32mzdask: use CONFIG_USE_PRIVATE_LIBGCC=y (2016-03-09 11:54:01 +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/20160310/2711ac23/attachment.sig>

  reply	other threads:[~2016-03-10 16:01 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 11:01 [U-Boot] [GIT PULL] u-boot-mips/master Daniel Schwierzeck
2016-03-10 16:01 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-23 16:58 Daniel Schwierzeck
2018-09-24 15:01 ` Tom Rini
2018-08-08 15:31 Daniel Schwierzeck
2018-08-10  3:27 ` Tom Rini
2017-11-28 21:13 Daniel Schwierzeck
2017-11-29  4:23 ` Tom Rini
2016-11-30 18:13 Daniel Schwierzeck
2016-11-30 19:01 ` Tom Rini
2016-11-30 19:21   ` Daniel Schwierzeck
2016-12-01  0:45 ` Tom Rini
2016-09-21 15:49 Daniel Schwierzeck
2016-09-22 15:35 ` Tom Rini
2016-06-10 10:52 Daniel Schwierzeck
2016-06-19 14:01 ` Tom Rini
2016-05-31  9:36 Daniel Schwierzeck
2016-05-31 14:50 ` Tom Rini
2016-05-26  0:13 Daniel Schwierzeck
2016-05-26 15:49 ` Tom Rini
2016-04-19 11:24 Daniel Schwierzeck
2016-04-21 11:25 ` Tom Rini
2016-01-16 20:45 Daniel Schwierzeck
2016-01-17  3:00 ` Tom Rini
2015-11-06 13:10 Daniel Schwierzeck
2015-11-07 13:18 ` Tom Rini
2015-08-24 11:24 Daniel Schwierzeck
2015-08-24 13:43 ` Tom Rini
2015-08-24 15:47   ` Daniel Schwierzeck
2015-07-02  9:34 Daniel Schwierzeck
2015-07-10 12:55 ` Tom Rini
2015-04-24 10:20 Daniel Schwierzeck
2015-04-28 14:51 ` Tom Rini
2015-01-30 14:42 Daniel Schwierzeck
2015-02-02 18:57 ` Tom Rini
2015-01-21 13:14 Daniel Schwierzeck
2015-01-23 21:56 ` Tom Rini
2014-11-27 15:25 Daniel Schwierzeck
2014-11-27 18:09 ` Tom Rini
2014-10-31 18:50 Daniel Schwierzeck
2014-11-04  2:33 ` Tom Rini
2014-04-20 11:28 Daniel Schwierzeck
2014-04-21  8:37 ` Masahiro Yamada
2014-04-21  9:10   ` Daniel Schwierzeck
2014-04-21  9:46     ` Masahiro Yamada
2014-04-23 15:15 ` Tom Rini
2014-03-04 22:49 Daniel Schwierzeck
2014-03-05  0:03 ` Tom Rini
2013-11-26 23:56 Daniel Schwierzeck
2013-12-02 16:12 ` Tom Rini
2013-11-15 23:03 Daniel Schwierzeck
2013-11-17 19:17 ` Tom Rini
2013-11-09 20:53 Daniel Schwierzeck
2013-11-11 17:30 ` Tom Rini
2013-11-11 19:00   ` Daniel Schwierzeck
2013-11-11 19:11     ` Tom Rini
2013-11-11 19:13 ` Tom Rini
2013-08-13 10:42 Daniel Schwierzeck
2013-08-13 13:13 ` Tom Rini
2013-07-23 22:42 Daniel Schwierzeck
2013-07-25 13:06 ` Tom Rini
2013-01-31  0:21 Daniel Schwierzeck
2013-01-31  0:30 ` Tom Rini
2013-01-16 10:11 Daniel Schwierzeck
2013-01-21 21:08 ` Tom Rini
2012-12-12 13:00 Daniel Schwierzeck
2012-12-12 13:52 ` Tom Rini
2012-12-08 20:57 Daniel Schwierzeck
2012-12-10 15:07 ` Tom Rini
2012-11-27 23:19 Daniel Schwierzeck
2012-11-28 13:04 ` Tom Rini
2012-10-16 22:01 Daniel Schwierzeck
2012-10-17 21:10 ` Tom Rini
2012-06-03 22:04 Daniel Schwierzeck
2012-06-07 21:39 ` Wolfgang Denk

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=20160310160111.GT23166@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 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.