Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@arm.com>, gdb-patches@sourceware.org
Cc: mark@klomp.org, Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] [Arm] Fix endianness handling for arm record self tests
Date: Tue, 9 Aug 2022 14:13:53 +0200	[thread overview]
Message-ID: <a1167868-056a-2e0f-6334-76db10bf03f7@suse.de> (raw)
In-Reply-To: <05ec382d-d10b-2dba-4948-ae4ec98b8d2d@arm.com>

On 8/9/22 14:09, Luis Machado wrote:
> On 8/9/22 13:08, Tom de Vries wrote:
>> On 8/9/22 13:48, Tom de Vries wrote:
>>> On 8/9/22 13:31, Luis Machado wrote:
>>>> I guess, though I was going to rework the patch based on Andrew's 
>>>> comments. Didn't get to it yet though.
>>>
>>> Ah, I hadn't seen Andrew's review.
>>>
>>> For some reason I wasn't cc-ed, perhaps that infuriating mailman CC 
>>> rewriting again.
>>>
>>
>> I've logged into the "Gdb-patches mailing list membership 
>> configuration"  and switched off "Avoid duplicate copies of messages", 
>> hopefully that will help.
> 
> Oh, is that the setting that makes things work OK? I'll have to try that.

I think this ( 
https://bugs.launchpad.net/mailman/+bug/1845751/comments/2 ) is a good 
description of the problem, and what the setting does.

Thanks,
- Tom


  reply	other threads:[~2022-08-09 12:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 10:12 Luis Machado via Gdb-patches
2022-08-08 12:30 ` Andrew Burgess via Gdb-patches
2022-08-10  8:47   ` Andrew Burgess via Gdb-patches
2022-08-09  9:43 ` Tom de Vries via Gdb-patches
2022-08-09  9:57   ` Tom de Vries via Gdb-patches
2022-08-15 12:13     ` Luis Machado via Gdb-patches
2022-08-09 11:31   ` Luis Machado via Gdb-patches
2022-08-09 11:48     ` Tom de Vries via Gdb-patches
2022-08-09 12:08       ` Tom de Vries via Gdb-patches
2022-08-09 12:09         ` Luis Machado via Gdb-patches
2022-08-09 12:13           ` Tom de Vries via Gdb-patches [this message]
2022-08-09 15:24             ` Mark Wielaard
2022-08-15 12:10   ` Luis Machado via Gdb-patches
2022-08-23 20:32 ` [PATCH,v2] " Luis Machado via Gdb-patches
2022-09-01  9:29   ` [PING][PATCH,v2] " Luis Machado via Gdb-patches
2022-09-06 10:39     ` Tom de Vries via Gdb-patches
2022-09-07  8:19       ` Luis Machado via Gdb-patches

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=a1167868-056a-2e0f-6334-76db10bf03f7@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=luis.machado@arm.com \
    --cc=mark@klomp.org \
    --cc=tdevries@suse.de \
    /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