From: Aleksandar Rikalo <Aleksandar.Rikalo@syrmia.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"arikalo@gmail.com" <arikalo@gmail.com>
Subject: [PATCH v3 1/2] sim: Add nanoMIPS port
Date: Tue, 13 Dec 2022 16:09:08 +0000 [thread overview]
Message-ID: <VI1PR0302MB348656712B6833C09F7952399CE39@VI1PR0302MB3486.eurprd03.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
Hello Mike,
Thanks again for your time.
I'll post a new version when those changes are in place.
Aleksandar
> let's circle back once GDB 13 branches, and some pending sim changes are
> merged. then you can rebase on top of that and send out a new version.
> -mike
next reply other threads:[~2022-12-13 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 16:09 Aleksandar Rikalo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-29 15:58 [PATCH 2/3] " Aleksandar Rikalo
2022-11-21 11:06 ` [PATCH v3 1/2] " Aleksandar Rikalo
2022-11-25 12:11 ` Mike Frysinger
2022-11-25 15:36 ` Aleksandar Rikalo
2022-12-12 11:11 ` Mike Frysinger
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=VI1PR0302MB348656712B6833C09F7952399CE39@VI1PR0302MB3486.eurprd03.prod.outlook.com \
--to=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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 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).