From: Amjad Ouled-Ameur <aouledameur@baylibre.com>
To: Florian Fainelli <f.fainelli@gmail.com>, jan.kiszka@siemens.com
Cc: linux-kernel@vger.kernel.org, narmstrong@baylibre.com,
kbingham@kernel.org, ouledameur.amjad@gmail.com
Subject: Re: [PATCH 0/3] scripts/gdb: timerlist: fix rb_node access and python errors
Date: Sun, 26 Mar 2023 16:26:40 +0200 [thread overview]
Message-ID: <cebe1ee8-280e-e0d8-bb78-f75ec2d471f2@baylibre.com> (raw)
In-Reply-To: <609742f5-c280-53fc-3b7d-84a5abf3459e@gmail.com>
Hi Florian,
Thank you for testing the series.
Regards,
Amjad
On 3/24/23 14:03, Florian Fainelli wrote:
> Hi Amjad, Jan,
>
> On 7/27/2022 7:14 AM, Amjad Ouled-Ameur wrote:
>> This patchset fixes use of lx-timerlist with kgdb.
>>
>> It has been tested on Amlogic libretech-cc s905X and works fine [0]
>>
>> [0]: https://pastebin.com/RAhQYh6L
>
> Was right about to submit similar fixes. The whole series is:
>
> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
>
> Jan, it would appear there were earlier attempts at fixing timerlist.py, however as of 6.3-rc3, none of those patches have been merged, can you take them? Thanks!
prev parent reply other threads:[~2023-03-26 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 14:14 [PATCH 0/3] scripts/gdb: timerlist: fix rb_node access and python errors Amjad Ouled-Ameur
2022-07-27 14:14 ` [PATCH 1/3] scripts/gdb: timerlist: use range instead of xrange Amjad Ouled-Ameur
2022-07-27 14:14 ` [PATCH 2/3] scripts/gdb: timerlist: fix rb_node access Amjad Ouled-Ameur
2022-07-27 14:14 ` [PATCH 3/3] scripts/gdb: timerlist: convert int chunks to str Amjad Ouled-Ameur
2023-03-24 13:03 ` [PATCH 0/3] scripts/gdb: timerlist: fix rb_node access and python errors Florian Fainelli
2023-03-26 14:26 ` Amjad Ouled-Ameur [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=cebe1ee8-280e-e0d8-bb78-f75ec2d471f2@baylibre.com \
--to=aouledameur@baylibre.com \
--cc=f.fainelli@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=ouledameur.amjad@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.