From: Shahab Vahedi <shahab.vahedi@gmail.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org,
Anton Kolesov <Anton.Kolesov@synopsys.com>,
Shahab Vahedi <shahab@synopsys.com>,
Francois Bedard <fbedard@synopsys.com>
Subject: Re: [PATCH v2 2/2] gdbserver: Add GNU/Linux support for ARC
Date: Wed, 7 Oct 2020 09:33:04 +0200 [thread overview]
Message-ID: <20201007073304.GB2011@gmail.com> (raw)
In-Reply-To: <abf43a08-0430-d8fd-01e0-aab4865c0d99@simark.ca>
Hi Simon,
On Tue, Oct 06, 2020 at 10:30:13PM -0400, Simon Marchi wrote:
> Oh, also it seems like we announce new gdbserver ports in gdb/NEWS, so
> can you please prepare a separate patch for that?
Sure! Does it really need to be a _separate_ patch?
On a different topic, can I still push my changes to "gdb-10-branch"?
Cheers,
Shahab
next prev parent reply other threads:[~2020-10-07 7:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 16:56 [PATCH] " Shahab Vahedi
2020-09-07 9:12 ` Shahab Vahedi
2020-09-16 2:29 ` [PING^2][PATCH] " Shahab Vahedi
2020-09-16 19:59 ` [PATCH] " Simon Marchi
2020-10-06 16:21 ` Shahab Vahedi
2020-10-06 16:42 ` [PATCH v2 1/2] arc: Rename "arc_gdbarch_features" struct Shahab Vahedi
2020-10-06 16:42 ` [PATCH v2 2/2] gdbserver: Add GNU/Linux support for ARC Shahab Vahedi
2020-10-07 2:28 ` Simon Marchi
2020-10-07 2:30 ` Simon Marchi
2020-10-07 7:33 ` Shahab Vahedi [this message]
2020-10-07 11:17 ` Simon Marchi
2020-10-07 7:20 ` Shahab Vahedi
2020-10-07 1:27 ` [PATCH v2 1/2] arc: Rename "arc_gdbarch_features" struct Simon Marchi
2020-10-07 15:58 ` [PUSHED master] " Shahab Vahedi
2020-10-07 15:58 ` [PUSHED master] gdbserver: Add GNU/Linux support for ARC Shahab Vahedi
2020-10-07 16:03 ` [PUSHED gdb-10-branch] arc: Rename "arc_gdbarch_features" struct Shahab Vahedi
2020-10-07 16:03 ` [PUSHED gdb-10-branch] gdbserver: Add GNU/Linux support for ARC Shahab Vahedi
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=20201007073304.GB2011@gmail.com \
--to=shahab.vahedi@gmail.com \
--cc=Anton.Kolesov@synopsys.com \
--cc=fbedard@synopsys.com \
--cc=gdb-patches@sourceware.org \
--cc=shahab@synopsys.com \
--cc=simark@simark.ca \
/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).