From: Andrew Morton <akpm@linux-foundation.org>
To: Glenn Washburn <development@efficientek.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
John Ogness <john.ogness@linutronix.de>,
Petr Mladek <pmladek@suse.com>,
Antonio Borneo <antonio.borneo@foss.st.com>,
linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] scripts/gdb: Create linux/vfs.py for VFS related GDB helpers
Date: Wed, 12 Apr 2023 12:21:21 -0700 [thread overview]
Message-ID: <20230412122121.79722bca514c454574d11b1b@linux-foundation.org> (raw)
In-Reply-To: <7bba4c065a8c2c47f1fc5b03a7278005b04db251.1677631565.git.development@efficientek.com>
On Tue, 28 Feb 2023 18:53:34 -0600 Glenn Washburn <development@efficientek.com> wrote:
> This will allow for more VFS specific GDB helpers to be collected in
> one place. Move utils.dentry_name into the vfs modules. Also a local
> variable in proc.py was changed from vfs to mnt to prevent a naming
> collision with the new vfs module.
checkpatch gets unhappy. Please add this addition?
--- a/scripts/gdb/linux/proc.py~scripts-gdb-create-linux-vfspy-for-vfs-related-gdb-helpers-fix
+++ a/scripts/gdb/linux/proc.py
@@ -1,3 +1,4 @@
+# SPDX-License-Identifier: GPL-2.0
#
# gdb helper commands and functions for Linux kernel debugging
#
_
next prev parent reply other threads:[~2023-04-12 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 0:53 [PATCH 0/2] GDB VFS utils Glenn Washburn
2023-03-01 0:53 ` [PATCH 1/2] scripts/gdb: Create linux/vfs.py for VFS related GDB helpers Glenn Washburn
2023-04-12 19:21 ` Andrew Morton [this message]
2023-03-01 0:53 ` [PATCH 2/2] scripts/gdb: Add GDB convenience functions $lx_dentry_name() and $lx_i_dentry() Glenn Washburn
2023-04-12 18:02 ` [PATCH 0/2] GDB VFS utils Florian Fainelli
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=20230412122121.79722bca514c454574d11b1b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=antonio.borneo@foss.st.com \
--cc=development@efficientek.com \
--cc=jan.kiszka@siemens.com \
--cc=john.ogness@linutronix.de \
--cc=kbingham@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).