public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] please pull u-boot-arc master
Date: Fri, 10 Apr 2015 16:29:30 +0000	[thread overview]
Message-ID: <1428683370.5325.12.camel@synopsys.com> (raw)
In-Reply-To: <1428681090.5325.8.camel@synopsys.com>

Hi Tom,

On Fri, 2015-04-10 at 18:51 +0300, Alexey Brodkin wrote:
> Hi Tom,
> 
> On Fri, 2015-04-10 at 09:59 +0300, Alexey Brodkin wrote:
> > Dear Tom,

> Please disregard initial pull-request because I've just added another
> critical fix in u-boot-arc repo and it would be good if it makes its way
> into the upcoming release, so here's an updated pull-request.

Looks like today is not the best of my days. Trying to squeeze one
important fix in the upcoming release I tested it improperly and so
clean build fails. For that reason I cooked another fix... on top of the
previous fix :(

And here's another (hopefully the last one for today) pull-request.

The following changes since commit
385a08a60f042061b004642d6b9bb6cfb794ad5a:

  ARM: zynq: Remove Jagan from list of maintainers (2015-04-08 18:43:51
-0400)

are available in the git repository at:

  git://git.denx.de/u-boot-arc.git 

for you to fetch changes up to a811492e4f386f79b122b210ac8e66915c27f767:

  arc: fix separate compilation of start.o (2015-04-10 19:22:40 +0300)

----------------------------------------------------------------
Alexey Brodkin (3):
      board: axs10x - support v3 mother-board
      arc: make sure _start is in the beginning of .text section
      arc: fix separate compilation of start.o

 arch/arc/cpu/u-boot.lds        |  1 +
 arch/arc/lib/Makefile          |  3 ++-
 board/synopsys/axs101/axs101.c | 14 ++++++++++++++
 board/synopsys/axs101/axs10x.h | 16 ++++++++++++++++
 board/synopsys/axs101/nand.c   |  7 +++++++
 include/configs/axs101.h       |  6 ++++++
 6 files changed, 46 insertions(+), 1 deletion(-)
 create mode 100644 board/synopsys/axs101/axs10x.h

Regards,
Alexey

  reply	other threads:[~2015-04-10 16:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 21:09 [U-Boot] please pull u-boot-arc master Alexey Brodkin
2015-01-10  3:12 ` Tom Rini
2015-01-15 20:39 ` [U-Boot] Please " Alexey Brodkin
2015-01-20 21:44   ` Tom Rini
2015-02-09 13:46   ` Alexey Brodkin
2015-02-09 20:26     ` Tom Rini
2015-02-09 13:47   ` Alexey Brodkin
2015-02-09 13:49   ` Alexey Brodkin
2015-02-09 13:52   ` Alexey Brodkin
2015-02-09 13:56   ` Alexey Brodkin
2015-02-13  6:23 ` [U-Boot] please " Alexey Brodkin
2015-02-18 12:35   ` Alexey Brodkin
2015-02-18 13:19     ` Alexey Brodkin
2015-04-03  6:56       ` Alexey Brodkin
2015-04-04  1:47         ` Tom Rini
2015-04-10  6:59         ` Alexey Brodkin
2015-04-10 15:51           ` Alexey Brodkin
2015-04-10 16:29             ` Alexey Brodkin [this message]
2015-04-10 18:49               ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2015-09-07 10:46 Alexey Brodkin
2015-09-08  0:19 ` Tom Rini
2015-05-18 12:30 Alexey Brodkin
2015-05-18 23:54 ` Tom Rini
2015-05-13 16:26 Alexey Brodkin
2015-05-14 19:14 ` Tom Rini
2014-04-25 14:24 Alexey Brodkin
2014-04-25 19:45 ` Tom Rini
2014-04-28  7:46   ` Alexey Brodkin
2014-05-27 14:28 ` Alexey Brodkin
2014-05-27 15:44   ` Tom Rini
2014-06-03 12:19 ` Alexey Brodkin
2014-06-05 15:46   ` 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=1428683370.5325.12.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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