From: Florian Fainelli <f.fainelli@gmail.com>
To: Glenn Washburn <development@efficientek.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: John Ogness <john.ogness@linutronix.de>,
Petr Mladek <pmladek@suse.com>,
Antonio Borneo <antonio.borneo@foss.st.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] GDB VFS utils
Date: Wed, 12 Apr 2023 11:02:46 -0700 [thread overview]
Message-ID: <64c4df35-6ecd-b1de-c2d9-f8acf1485488@gmail.com> (raw)
In-Reply-To: <cover.1677631565.git.development@efficientek.com>
On 2/28/23 16:53, Glenn Washburn wrote:
> Hi all,
>
> I've created a couple GDB convenience functions that I found useful when
> debugging some VFS issues and figure others might find them useful. For
> instance, they are useful in setting conditional breakpoints on VFS
> functions where you only care if the dentry path is a certain value. I
> took the opportunity to create a new "vfs" python module to give VFS
> related utilities a home.
Andrew, any chance you could pick up those two patches from Glenn:
https://lore.kernel.org/all/7bba4c065a8c2c47f1fc5b03a7278005b04db251.1677631565.git.development@efficientek.com/
https://lore.kernel.org/all/c9a5ad8efbfbd2cc6559e082734eed7628f43a16.1677631565.git.development@efficientek.com/
Thanks!
--
Florian
prev parent reply other threads:[~2023-04-12 18:02 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
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 ` Florian Fainelli [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=64c4df35-6ecd-b1de-c2d9-f8acf1485488@gmail.com \
--to=f.fainelli@gmail.com \
--cc=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).