From: Aleksandar Rikalo <Aleksandar.Rikalo@syrmia.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
"arikalo@gmail.com" <arikalo@gmail.com>,
Nick Clifton <nickc@redhat.com>
Subject: [PATCH v4] Add support for nanoMIPS architecture
Date: Fri, 25 Nov 2022 14:57:36 +0000 [thread overview]
Message-ID: <VI1PR0302MB3486747C191DA0EA6E862CD49C0E9@VI1PR0302MB3486.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2211242215400.41742@angie.orcam.me.uk>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
> Actually using EM_NANOMIPS throughout just as in v3 would make more sense
> than EM_IMG1. The sole reason for the existence of EM_IMG1 was to have a
> placeholder before the name of nanoMIPS project could have been disclosed
> to the public. I remember this being discussed, though I can't find a
> reference now (perhaps it was internal).
>
> Maciej
That makes sense to me too. Thank you!
I will change it in v5.
Aleksandar
prev parent reply other threads:[~2022-11-25 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 15:45 Aleksandar Rikalo
2022-11-25 11:22 ` Maciej W. Rozycki
2022-11-25 14:57 ` Aleksandar Rikalo [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=VI1PR0302MB3486747C191DA0EA6E862CD49C0E9@VI1PR0302MB3486.eurprd03.prod.outlook.com \
--to=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.com \
--cc=binutils@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=nickc@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).