From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] arch/mips: introduce mips32r3 and mips64r3
Date: Mon, 4 Feb 2019 17:33:33 +0100 [thread overview]
Message-ID: <20190204173333.18c9069e@windsurf> (raw)
In-Reply-To: <20190130201224.6555-1-patrickdepinguin@gmail.com>
On Wed, 30 Jan 2019 21:12:22 +0100
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
>
> It's unclear why Buildroot only defined MIPS 32/64 releases 1, 2, 5 and 6
> while 3 exists as well.
>
> Interesting fact:
> "Release 4 was skipped because the number four is perceived as unlucky in
> many Asian cultures."
> https://en.wikipedia.org/wiki/MIPS_architecture#MIPS32/MIPS64
>
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
> arch/Config.in.mips | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
Patch series applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-04 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 20:12 [Buildroot] [PATCH 1/3] arch/mips: introduce mips32r3 and mips64r3 Thomas De Schampheleire
2019-01-30 20:12 ` [Buildroot] [PATCH 2/3] arch/mips: add (Marvell) Octeon II processor Thomas De Schampheleire
2019-01-30 20:12 ` [Buildroot] [PATCH 3/3] arch/mips: add (Marvell) Octeon III processor Thomas De Schampheleire
2019-01-30 20:29 ` Thomas Petazzoni
2019-01-30 20:41 ` Thomas De Schampheleire
2019-01-31 21:34 ` Arnout Vandecappelle
2019-02-04 16:33 ` Thomas Petazzoni [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=20190204173333.18c9069e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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