From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Christina Schimpe <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/1] gdb, infcmd: remove redundant ERROR_NO_INFERIOR in continue_command
Date: Mon, 27 Mar 2023 13:41:59 +0200 [thread overview]
Message-ID: <CAJVr-ENunmkoA_jtt-GJ+Y+NN94WMKnnx8r0B_DGuJHLB1RGkQ@mail.gmail.com> (raw)
In-Reply-To: <20230327095425.601412-2-christina.schimpe@intel.com>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Mon, Mar 27, 2023 at 11:55 AM Christina Schimpe <
christina.schimpe@intel.com> wrote:
> From: Nils-Christian Kempke <nils-christian.kempke@intel.com>
>
> The ERROR_NO_INFERIOR macro is already called at the beginning of the
> function continue_command. Since target/inferior are not switched
> in-between,
> the second call to it is redundant.
>
> Co-Authored-By: Christina Schimpe <christina.schimpe@intel.com>
>
>
I think it's good to go in.
next prev parent reply other threads:[~2023-03-27 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 9:54 [PATCH v2 0/1] Remove " Christina Schimpe
2023-03-27 9:54 ` [PATCH v2 1/1] gdb, infcmd: remove " Christina Schimpe
2023-03-27 11:41 ` Alexandra Petlanova Hajkova [this message]
2023-03-27 13:31 ` Andrew Burgess
2023-03-29 11:01 ` Schimpe, Christina
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=CAJVr-ENunmkoA_jtt-GJ+Y+NN94WMKnnx8r0B_DGuJHLB1RGkQ@mail.gmail.com \
--to=ahajkova@redhat.com \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.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).