From: Florian Fainelli <f.fainelli@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [PATCH v2 0/3] MIPS: add uImage build target
Date: Sun, 1 Sep 2013 20:06:24 +0100 [thread overview]
Message-ID: <CAGVrzca5i2CgXYOSobOz+9=gLg7syZueq0X-zqg_bQD=vpyDjw@mail.gmail.com> (raw)
In-Reply-To: <1377877362-15650-1-git-send-email-james.hogan@imgtec.com>
2013/8/30 James Hogan <james.hogan@imgtec.com>:
> This adds a uImage build target for MIPS. The first two patches clean up
> the Makefiles slightly to allow the load and entry address to be passed
> nicely to arch/mips/boot/Makefile, and the final patch adds the uImage
> targets.
>
> Signed-off-by: James Hogan <james.hogan@imgtec.com>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: linux-mips@linux-mips.org
>
> Changes in v2:
> - Split into several patches to add refactoring which avoids duplicated
> load/entry address calculations (Florian).
> - Disable uImage targets when load address < 0xffffffff80000000 (e.g.
> SGI IP27).
>
> James Hogan (3):
> MIPS: refactor boot and boot/compressed rules
> MIPS: refactor load/entry address calculations
> MIPS: add uImage build target
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Looks good, thanks James!
--
Florian
prev parent reply other threads:[~2013-09-01 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 15:42 [PATCH v2 0/3] MIPS: add uImage build target James Hogan
2013-08-30 15:42 ` James Hogan
2013-08-30 15:42 ` [PATCH v2 1/3] MIPS: refactor boot and boot/compressed rules James Hogan
2013-08-30 15:42 ` James Hogan
2013-08-30 15:42 ` [PATCH v2 2/3] MIPS: refactor load/entry address calculations James Hogan
2013-08-30 15:42 ` James Hogan
2013-08-30 15:42 ` [PATCH v2 3/3] MIPS: add uImage build target James Hogan
2013-08-30 15:42 ` James Hogan
2013-09-01 19:06 ` Florian Fainelli [this message]
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='CAGVrzca5i2CgXYOSobOz+9=gLg7syZueq0X-zqg_bQD=vpyDjw@mail.gmail.com' \
--to=f.fainelli@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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.