public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Chaitanya S Prakash <chaitanyas.prakash@arm.com>
Cc: Will Deacon <will@kernel.org>,
	Anshuman.Khandual@arm.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH V2] Documentation/arm64: Add ptdump documentation
Date: Wed, 21 Jun 2023 10:04:03 -0600	[thread overview]
Message-ID: <87ttv0pzt8.fsf@meer.lwn.net> (raw)
In-Reply-To: <168736253462.605140.8006082140297031307.b4-ty@arm.com>

Catalin Marinas <catalin.marinas@arm.com> writes:

> On Mon, 19 Jun 2023 14:08:02 +0530, Chaitanya S Prakash wrote:
>> ptdump is a debugfs interface used to dump the kernel page tables. It
>> provides a comprehensive overview about the kernel's virtual memory
>> layout, page table entries and associated page attributes. A document
>> detailing how to enable ptdump in the kernel and analyse its output has
>> been added.
>> 
>> Changes in V2:
>> 
>> [...]
>
> Applied to arm64 (for-next/doc), thanks! I did some tidying up, minor
> fixes.
>
> [1/1] Documentation/arm64: Add ptdump documentation
>       https://git.kernel.org/arm64/c/a0238ada560f

Note that this will generate a conflict with the arm64 documentation
move, which I dropped into -next today.  It's easily enough fixed up
top, but if you'd rather carry the directory move in your tree just say
the word.

Thanks,

jon

  reply	other threads:[~2023-06-21 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19  8:38 [PATCH V2] Documentation/arm64: Add ptdump documentation Chaitanya S Prakash
2023-06-21 15:49 ` Catalin Marinas
2023-06-21 16:04   ` Jonathan Corbet [this message]
2023-06-22  7:51     ` Catalin Marinas
2023-06-23 19:29       ` Jonathan Corbet
2023-06-23 20:32         ` Catalin Marinas

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=87ttv0pzt8.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=Anshuman.Khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=chaitanyas.prakash@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@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