From: Paul Burton <paul.burton@imgtec.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] MIPS: unify start.S
Date: Fri, 30 Jan 2015 12:22:19 +0000 [thread overview]
Message-ID: <20150130122219.GL6116@NP-P-BURTON> (raw)
In-Reply-To: <CACUy__WGfTttveVg5Nrb95kav=2gy8Dne+mv+OBb55gNS4uUuQ@mail.gmail.com>
On Thu, Jan 29, 2015 at 02:48:59PM +0100, Daniel Schwierzeck wrote:
> Hi Paul,
>
> 2015-01-29 11:04 GMT+01:00 Paul Burton <paul.burton@imgtec.com>:
> > Currently we have mips32-specific & mips64-specific versions of start.S,
> > which are very similar. This short series adapts the mips32 start.S to
> > also be suitable for mips64 systems & then shares that single copy
> > between mips32 & mips64 builds.
> >
> > Paul Burton (4):
> > MIPS: use asm.h macros in mips32 start.S
> > MIPS: handle mips64 relocs in mips32 start.S
> > MIPS: handle mips64 ST0_KX bit in mips32 start.S
> > MIPS: share start.S between mips32 & mips64
> >
>
> very appreciated, thanks. But I'd like to replace patch 4/4 with
>
> http://patchwork.ozlabs.org/patch/434556/
> http://patchwork.ozlabs.org/patch/434555/
>
> what do you think?
>
> --
> - Daniel
Hi Daniel,
Seems good to me :)
Paul
prev parent reply other threads:[~2015-01-30 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 10:04 [U-Boot] [PATCH 0/4] MIPS: unify start.S Paul Burton
2015-01-29 10:04 ` [U-Boot] [PATCH 1/4] MIPS: use asm.h macros in mips32 start.S Paul Burton
2015-01-29 10:04 ` [U-Boot] [PATCH 2/4] MIPS: handle mips64 relocs " Paul Burton
2015-01-29 10:04 ` [U-Boot] [PATCH 3/4] MIPS: handle mips64 ST0_KX bit " Paul Burton
2015-01-29 10:04 ` [U-Boot] [PATCH 4/4] MIPS: share start.S between mips32 & mips64 Paul Burton
2015-01-29 13:48 ` [U-Boot] [PATCH 0/4] MIPS: unify start.S Daniel Schwierzeck
2015-01-30 12:22 ` Paul Burton [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=20150130122219.GL6116@NP-P-BURTON \
--to=paul.burton@imgtec.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