linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
	linux-kernel@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Kieran Bingham <kbingham@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Dennis Zhou <dennis@kernel.org>,
	Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@gentwo.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Alexander Potapenko <glider@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Daniel Gomez <da.gomez@samsung.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Uladzislau Rezki <urezki@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	Kuan-Ying Lee <kuan-ying.lee@canonical.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Etienne Buira <etienne.buira@free.fr>,
	Antonio Quartulli <antonio@mandelbit.com>,
	Illia Ostapyshyn <illia@yshyn.com>,
	"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
	"open list:PER-CPU MEMORY ALLOCATOR" <linux-mm@kvack.org>,
	"open list:GENERIC PM DOMAINS" <linux-pm@vger.kernel.org>,
	"open list:KASAN" <kasan-dev@googlegroups.com>,
	"open list:MAPLE TREE" <maple-tree@lists.infradead.org>,
	"open list:MODULE SUPPORT" <linux-modules@vger.kernel.org>,
	"open list:PROC FILESYSTEM" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 08/16] MAINTAINERS: Include GDB scripts under MEMORY MANAGEMENT entry
Date: Fri, 27 Jun 2025 19:10:06 +0200	[thread overview]
Message-ID: <04116d0f-2815-4583-853e-e4295fb3d014@redhat.com> (raw)
In-Reply-To: <20250625231053.1134589-9-florian.fainelli@broadcom.com>

On 26.06.25 01:10, Florian Fainelli wrote:
> Include the GDB scripts file under scripts/gdb/linux/ that deal with
> memory mamagenement code under the MEMORY MANAGEMENT subsystem since
> they parses internal data structures that depend upon that subsystem.
> 
> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
>   MAINTAINERS | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cad5d613cab0..52b37196d024 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15812,6 +15812,10 @@ F:	include/linux/mmu_notifier.h
>   F:	include/linux/pagewalk.h
>   F:	include/trace/events/ksm.h
>   F:	mm/
> +F:	scripts/gdb/linux/mm.py
> +F:	scripts/gdb/linux/page_owner.py
> +F:	scripts/gdb/linux/pgtable.py
> +F:	scripts/gdb/linux/slab.py

Probably they should go to the corresponding sub-sections. At least slab.py?

-- 
Cheers,

David / dhildenb


  reply	other threads:[~2025-06-27 17:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 23:10 [PATCH 00/16] MAINTAINERS: Include GDB scripts under their relevant subsystems Florian Fainelli
2025-06-25 23:10 ` [PATCH 01/16] MAINTAINERS: Include clk.py under COMMON CLK FRAMEWORK entry Florian Fainelli
2025-07-24 21:24   ` Stephen Boyd
2025-06-25 23:10 ` [PATCH 02/16] MAINTAINERS: Include device.py under DRIVER CORE entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 03/16] MAINTAINERS: Include genpd.py under GENERIC PM DOMAINS entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 04/16] MAINTAINERS: Include radixtree.py under GENERIC RADIX TREE entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 05/16] MAINTAINERS: Include interrupts.py under IRQ SUBSYSTEM entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 06/16] MAINTAINERS: Include kasan.py under KASAN entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 07/16] MAINTAINERS: Include mapletree.py under MAPLE TREE entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 08/16] MAINTAINERS: Include GDB scripts under MEMORY MANAGEMENT entry Florian Fainelli
2025-06-27 17:10   ` David Hildenbrand [this message]
2025-07-24 21:27     ` Florian Fainelli
2025-06-25 23:10 ` [PATCH 09/16] MAINTAINERS: Include modules.py under MODULE SUPPORT entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 10/16] MAINTAINERS: Include cpus.py under PER-CPU MEMORY ALLOCATOR entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 11/16] MAINTAINERS: Include timerlist.py under POSIX CLOCKS and TIMERS entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 12/16] MAINTAINERS: Include dmesg.py under PRINTK entry Florian Fainelli
2025-06-26  8:43   ` John Ogness
2025-07-24 21:27     ` Florian Fainelli
2025-06-25 23:10 ` [PATCH 13/16] MAINTAINERS: Include proc.py under PROC FILESYSTEM entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 14/16] MAINTAINERS: Include vmalloc.py under VMALLOC entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 15/16] MAINTAINERS: Include xarray.py under XARRAY entry Florian Fainelli
2025-06-25 23:10 ` [PATCH 16/16] MAINTAINERS: Include vfs.py under FILESYSTEMS entry Florian Fainelli
2025-06-26 16:17 ` [PATCH 00/16] MAINTAINERS: Include GDB scripts under their relevant subsystems Liam R. Howlett
2025-06-26 16:39   ` Florian Fainelli
2025-06-27  7:55     ` Jan Kara
2025-06-27 16:09       ` Florian Fainelli
2025-06-26 16:48   ` Jan Kiszka

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=04116d0f-2815-4583-853e-e4295fb3d014@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=anna-maria@linutronix.de \
    --cc=antonio@mandelbit.com \
    --cc=brauner@kernel.org \
    --cc=cl@gentwo.org \
    --cc=da.gomez@samsung.com \
    --cc=dakr@kernel.org \
    --cc=dennis@kernel.org \
    --cc=dvyukov@google.com \
    --cc=etienne.buira@free.fr \
    --cc=florian.fainelli@broadcom.com \
    --cc=frederic@kernel.org \
    --cc=glider@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=iii@linux.ibm.com \
    --cc=illia@yshyn.com \
    --cc=jack@suse.cz \
    --cc=jan.kiszka@siemens.com \
    --cc=john.ogness@linutronix.de \
    --cc=kasan-dev@googlegroups.com \
    --cc=kbingham@kernel.org \
    --cc=kent.overstreet@linux.dev \
    --cc=kuan-ying.lee@canonical.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=petr.pavlu@suse.com \
    --cc=pmladek@suse.com \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=samitolvanen@google.com \
    --cc=sboyd@kernel.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=urezki@gmail.com \
    --cc=vincenzo.frascino@arm.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).