From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Cc: gregkh@linuxfoundation.org, jan.kiszka@siemens.com,
kbingham@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mingo@redhat.com, rppt@kernel.org,
vbabka@suse.cz, x86@kernel.org
Subject: Re: [PATCH v5] scripts/gdb: add mm introspection utils
Date: Fri, 13 Jan 2023 20:03:56 -0800 [thread overview]
Message-ID: <20230113200356.d30a23872521f0cf24ed996c@linux-foundation.org> (raw)
In-Reply-To: <20230113175151.22278-1-dmitrii.bundin.a@gmail.com>
On Fri, 13 Jan 2023 20:51:51 +0300 Dmitrii Bundin <dmitrii.bundin.a@gmail.com> wrote:
> Changes in v5: https://lore.kernel.org/all/20230102171014.31408-1-dmitrii.bundin.a@gmail.com/
> - Added SPDX line
Almost.
--- a/scripts/gdb/linux/mm.py~scripts-gdb-add-mm-introspection-utils-v5
+++ a/scripts/gdb/linux/mm.py
@@ -1,3 +1,4 @@
+# SPDX-License-Identifier: GPL-2.0-only
#
# gdb helper commands and functions for Linux kernel debugging
#
@@ -6,8 +7,6 @@
# Authors:
# Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
#
-# This work is licensed under the terms of the GNU GPL version 2.
-#
import gdb
--- a/scripts/gdb/vmlinux-gdb.py~scripts-gdb-add-mm-introspection-utils-v5
+++ a/scripts/gdb/vmlinux-gdb.py
@@ -37,3 +37,4 @@ else:
import linux.clk
import linux.genpd
import linux.device
+ import linux.mm
_
next prev parent reply other threads:[~2023-01-14 4:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 16:35 [PATCH] " Dmitrii Bundin
2022-12-30 20:06 ` Mike Rapoport
2022-12-31 17:14 ` Dmitrii Bundin
2023-01-01 7:51 ` Mike Rapoport
2023-01-01 17:23 ` [PATCH v3] " Dmitrii Bundin
2023-01-02 8:59 ` Jan Kiszka
2023-01-02 17:10 ` [PATCH v4] " Dmitrii Bundin
2023-01-02 18:28 ` Mike Rapoport
2023-01-12 20:16 ` Greg KH
2023-01-13 17:51 ` [PATCH v5] " Dmitrii Bundin
2023-01-14 4:03 ` Andrew Morton [this message]
2022-12-30 21:37 ` [PATCH] " Andrew Morton
2022-12-31 17:26 ` Dmitrii Bundin
2022-12-31 17:12 ` [PATCH v2] " Dmitrii Bundin
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=20230113200356.d30a23872521f0cf24ed996c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dmitrii.bundin.a@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=x86@kernel.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