Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Sven Schnelle <svens@stackframe.org>
Cc: gdb-patches@sourceware.org, Helge Deller <deller@gmx.de>,
	John David Anglin <dave.anglin@bell.net>,
	binutils@sourceware.org
Subject: Re: [PATCH v3] gdb/hppa: guess g packet size
Date: Mon, 10 Nov 2025 17:51:44 -0500	[thread overview]
Message-ID: <1f2edf48-ac23-4366-bbbc-aacdcd1582ba@simark.ca> (raw)
In-Reply-To: <87v7jhh8id.fsf@stackframe.org>



On 2025-11-10 16:39, Sven Schnelle wrote:
> Simon Marchi <simark@simark.ca> writes:
> 
>> On 11/10/25 4:34 PM, Sven Schnelle wrote:
>>> Simon Marchi <simark@simark.ca> writes:
>>>
>>>>> +	  warning (_("target returned a target description this gdb doesn't "
>>>>> +		     "support for the HP/PA architecture"));
>>>>
>>>> Good idea to put out a warning.  I would suggesting some minor changes
>>>> to the message:
>>>>
>>>> 	  warning (_("The target returned a target description but this gdb "
>>>> 		     "doesn't support target descriptions for the HP/PA
>>>> 		     "architecture"));
>>>>
>>>> Just thinking out loud: it would actually be nice to have this warning
>>>> for all architectures that don't support target descriptions, if there
>>>> was a way to put it at a single common place.
>>>>
>>>> Other than that, the patch looks fine.
>>>>
>>>> Approved-By: Simon Marchi <simon.marchi@efficios.com>
>>>>
>>>> Do you have push access or would you like me to push the patch on your
>>>> behalf (with the modification proposed above)?
>>>
>>> I don't have push acess - would appreciate if you could adjust the
>>> message and push it.
>>
>> Done, thanks.  I even extended the message to:
>>
>> 	  warning (_("The target returned a target description but this GDB "
>> 		     "doesn't support target descriptions for the HP/PA"
>> 		     "architecture.  Assuming standard 32-bit register"
>> 		     "layout."));
> 
> Thanks! One nit pick - I think there's a superfluous whitespace before
> 'Assuming standard 32-bit...'

The GNU standard calls for two spaces after a period (in comments as
well).

Simon

      reply	other threads:[~2025-11-10 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 21:07 Sven Schnelle
2025-11-10 21:29 ` Simon Marchi
2025-11-10 21:34   ` Sven Schnelle
2025-11-10 21:38     ` Simon Marchi
2025-11-10 21:39       ` Sven Schnelle
2025-11-10 22:51         ` Simon Marchi [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=1f2edf48-ac23-4366-bbbc-aacdcd1582ba@simark.ca \
    --to=simark@simark.ca \
    --cc=binutils@sourceware.org \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=gdb-patches@sourceware.org \
    --cc=svens@stackframe.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