From: Peng Liu <pngliu@hotmail.com>
To: kbingham@kernel.org
Cc: jan.kiszka@siemens.com, linux-kernel@vger.kernel.org,
Peng Liu <liupeng17@lenovo.com>
Subject: Re: [PATCH 1/3] scripts/gdb: fix lx-timerlist for struct timequeue_head change
Date: Wed, 31 Aug 2022 10:01:57 +0800 [thread overview]
Message-ID: <TYCP286MB2146AB9675875CDB8DC6F5F7C6789@TYCP286MB2146.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <TYYP286MB176395568EC0A0C49C63C658C6719@TYYP286MB1763.JPNP286.PROD.OUTLOOK.COM>
ping
On 2022/8/22 17:29, Peng Liu wrote:
> ping
>
> On 2022/8/4 16:49, Peng Liu wrote:
>> ping
>>
>> On 2022/7/20 20:27, pngliu@hotmail.com wrote:
>>> From: Peng Liu <liupeng17@lenovo.com>
>>>
>>> commit 511885d7061e ("lib/timerqueue: Rely on rbtree semantics for next
>>> timer") changed struct timerqueue_head, and so print_active_timers()
>>> should be changed accordingly with its way to interpret the structure.
>>>
>>> Signed-off-by: Peng Liu <liupeng17@lenovo.com>
>>> ---
>>> scripts/gdb/linux/timerlist.py | 3 +--
>>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/scripts/gdb/linux/timerlist.py
>>> b/scripts/gdb/linux/timerlist.py
>>> index 071d0dd5a634..44e39dc3eb64 100644
>>> --- a/scripts/gdb/linux/timerlist.py
>>> +++ b/scripts/gdb/linux/timerlist.py
>>> @@ -43,8 +43,7 @@ def print_timer(rb_node, idx):
>>> def print_active_timers(base):
>>> - curr = base['active']['next']['node']
>>> - curr = curr.address.cast(rbtree.rb_node_type.get_type().pointer())
>>> + curr = base['active']['rb_root']['rb_leftmost']
>>> idx = 0
>>> while curr:
>>> yield print_timer(curr, idx)
next prev parent reply other threads:[~2022-08-31 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 12:27 pngliu
2022-08-04 8:49 ` Peng Liu
2022-08-22 9:29 ` Peng Liu
2022-08-31 2:01 ` Peng Liu [this message]
2022-08-31 15:00 ` Jan Kiszka
2023-03-21 6:18 Peng Liu
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=TYCP286MB2146AB9675875CDB8DC6F5F7C6789@TYCP286MB2146.JPNP286.PROD.OUTLOOK.COM \
--to=pngliu@hotmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liupeng17@lenovo.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
all inboxes | Powered by JetHome®