From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Pedro Alves <pedro@palves.net>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "tom@tromey.com" <tom@tromey.com>,
"aburgess@redhat.com" <aburgess@redhat.com>,
"eliz@gnu.org" <eliz@gnu.org>
Subject: RE: [PATCH v4 1/3] gdb: Make global feature array a per-remote target array
Date: Mon, 30 Jan 2023 14:34:07 +0000 [thread overview]
Message-ID: <CY4PR11MB2005070C362B51E3D53974D5F9D39@CY4PR11MB2005.namprd11.prod.outlook.com> (raw)
In-Reply-To: <eebae95e-cfb8-671b-5650-17704e7f5936@palves.net>
Hi,
Thank you for the review.
> On 2022-12-21 1:39 p.m., Christina Schimpe wrote:
>
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -3,6 +3,20 @@
> >
> > *** Changes since GDB 13
> >
> > +* Multi-target feature configuration
> > +
> > + GDB now supports the individual configuration of remote target's
> > + feature
>
> I think you meant for "remote target" to be plural, so it should be written with
> the approstrophe after the plural "s", like "remote targets'". Otherwise, if you
> really meant singular, then an article seems missing after "of", as in
>
> "configuration of a/the remote target's"
Yes, I meant plural and fixed it with "remote targets'".
> > + sets. Based on the current selection of a target, the commands
> > + 'set remote <name>-packet (on|off|auto)' and 'show remote
> > + <name>-packet' can be used to configure a target's feature packet
> > + and to display its configuration, respectively.
> > +
> > + The configuration of the packet itself applies to the currently
> > + selected target (if available). If no target is selected, it
> > + applies to future remote connections. Similarly, the show commands
> > + print the configuration of the currently selected target. If no
> > + remote target is selected, the default configuration for future connections is
> shown.
> > +
> > * MI version 1 has been removed.
>
> ...
>
> >
> > +/* Description of a remote packet. */
> > +
> > +struct packet_description
> > + {
>
> Please fix indentation of {, and then the struct's fields accordingly (and possibly
> reflow comments). The "{" should be at column zero. No need to repost the
> patch for this.
Fixed.
> > + /* Name of the packet used for gdb output. */
> > + const char *name;
> > +
> > + /* Title of the packet, used by the set/show remote name-packet
> > + commands to identify the individual packages and gdb output. */
> > + const char *title;
> > +
>
> Remove spurious empty line after last field.
Fixed.
> > + };
> > +
> > +/* Configuration of a remote packet. */
> > +
> > +struct packet_config
> > + {
>
> Ditto.
Fixed.
> > + /* If auto, GDB auto-detects support for this packet or feature,
> > + either through qSupported, or by trying the packet and looking
> > + at the response. If true, GDB assumes the target supports this
> > + packet. If false, the packet is disabled. Configs that don't
> > + have an associated command always have this set to auto. */
> > + enum auto_boolean detect;
> > +
> > + /* Does the target support this packet? */
> > + enum packet_support support;
> > + };
> > +
> This is OK with the nits above fixed. Thank you!
I have pushed this change with the nits addressed.
Best Regards,
Christina
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2023-01-30 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 13:39 [PATCH v4 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-12-21 13:39 ` [PATCH v4 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-12-21 14:08 ` Eli Zaretskii
2023-01-23 17:42 ` Pedro Alves
2023-01-30 14:34 ` Schimpe, Christina [this message]
2022-12-21 13:39 ` [PATCH v4 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-12-21 14:13 ` Eli Zaretskii
2023-01-23 17:43 ` Pedro Alves
2023-01-30 14:34 ` Schimpe, Christina
2022-12-21 13:39 ` [PATCH v4 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2023-01-23 17:46 ` Pedro Alves
2023-01-30 14:35 ` Schimpe, Christina
2023-01-16 8:58 ` [PING][PATCH v4 0/3] Apply fixme notes for multi-target support 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=CY4PR11MB2005070C362B51E3D53974D5F9D39@CY4PR11MB2005.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tom@tromey.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).