The patch titled Subject: scripts/gdb: add utils.read_ulong() has been removed from the -mm tree. Its filename was scripts-gdb-add-utilsread_ulong.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: John Ogness <john.ogness@xxxxxxxxxxxxx> Subject: scripts/gdb: add utils.read_ulong() Patch series "update gdb scripts for lockless printk ringbuffer". When we brought in the new lockless printk ringbuffer, we overlooked the gdb scripts. Here are a set of patches to implement gdb support for the new ringbuffer. This patch (of 2): Add a function for reading unsigned long values, which vary in size depending on the architecture. Link: https://lkml.kernel.org/r/20200814212525.6118-1-john.ogness@xxxxxxxxxxxxx Link: https://lkml.kernel.org/r/20200814212525.6118-2-john.ogness@xxxxxxxxxxxxx Signed-off-by: John Ogness <john.ogness@xxxxxxxxxxxxx> Reviewed-by: Nick Desaulniers <ndesaulniers@xxxxxxxxxx> Tested-by: Nick Desaulniers <ndesaulniers@xxxxxxxxxx> Tested-by: Petr Mladek <pmladek@xxxxxxxx> Cc: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> Cc: Baoquan He <bhe@xxxxxxxxxx> Cc: Dave Young <dyoung@xxxxxxxxxx> Cc: Vivek Goyal <vgoyal@xxxxxxxxxx> Cc: Jonathan Corbet <corbet@xxxxxxx> Cc: Kieran Bingham <kbingham@xxxxxxxxxx> Cc: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> Cc: Steven Rostedt <rostedt@xxxxxxxxxxx> Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> Cc: David Laight <David.Laight@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- scripts/gdb/linux/utils.py | 7 +++++++ 1 file changed, 7 insertions(+) --- a/scripts/gdb/linux/utils.py~scripts-gdb-add-utilsread_ulong +++ a/scripts/gdb/linux/utils.py @@ -123,6 +123,13 @@ def read_u64(buffer, offset): return read_u32(buffer, offset + 4) + (read_u32(buffer, offset) << 32) +def read_ulong(buffer, offset): + if get_long_type().sizeof == 8: + return read_u64(buffer, offset) + else: + return read_u32(buffer, offset) + + target_arch = None _ Patches currently in -mm which might be from john.ogness@xxxxxxxxxxxxx are