linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: rdunlap@infradead.org, sfr@canb.auug.org.au,
	kent.overstreet@linux.dev,  surenb@google.com,
	linux-mm@kvack.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] Documentation fixes for memory allocation profiling
Date: Tue, 26 Mar 2024 16:14:46 -0700	[thread overview]
Message-ID: <20240326231453.1206227-1-surenb@google.com> (raw)

With the introduction of [1] kernel-doc can handle _noprof function names. 
This patchset changes back _noprof documentation changes introduced in
memory allocation profiling patchset [2].
Changes are split into several patches, each undoing changes in a specific
patch from the original patchset so that it's easy to squash the fix into
the initial patch if Andrew wants to do that.
Changes apply cleanly over mm-unstable and are tested with [1] applied.

[1] https://lore.kernel.org/all/20240326054149.2121-1-rdunlap@infradead.org/
[2] https://lore.kernel.org/all/20240321163705.3067592-1-surenb@google.com/

Suren Baghdasaryan (6):
  Documentation: rhashtable: undo _noprof additions in the documentation
  Documentation: mm: undo _noprof additions in the documentation
  Documentation: mempool: undo _noprof additions in the documentation
  Documentation: mm: vmalloc: undo _noprof additions in the
    documentation
  Documentation: mm: percpu: undo _noprof additions in the documentation
  Documentation: mm/slab: undo _noprof additions in the documentation

 lib/rhashtable.c |  6 +++---
 mm/mempolicy.c   |  6 +++---
 mm/mempool.c     |  2 +-
 mm/nommu.c       |  8 ++++----
 mm/page_alloc.c  |  8 ++++----
 mm/percpu.c      |  2 +-
 mm/slub.c        |  2 +-
 mm/util.c        | 10 +++++-----
 mm/vmalloc.c     | 14 +++++++-------
 9 files changed, 29 insertions(+), 29 deletions(-)


base-commit: 4aaccadb5c04dd4d4519c8762a38010a32d904a3
prerequisite-patch-id: 1c2be401fcd818b167ef7d506a2fb87fea230835
prerequisite-patch-id: d3c1b90bc5ee32295962c5d30bd79dfb6eb774c3
prerequisite-patch-id: 25e37766c40250d564a0c198e2af01a9aae33c92
prerequisite-patch-id: ed3859d70637371a854c212aa08db8f28edbede4
-- 
2.44.0.396.g6e790dbe36-goog



             reply	other threads:[~2024-03-26 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 23:14 Suren Baghdasaryan [this message]
2024-03-26 23:14 ` [PATCH 1/6] Documentation: rhashtable: undo _noprof additions in the documentation Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 2/6] Documentation: mm: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 3/6] Documentation: mempool: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 4/6] Documentation: mm: vmalloc: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 5/6] Documentation: mm: percpu: " Suren Baghdasaryan
2024-03-26 23:14 ` [PATCH 6/6] Documentation: mm/slab: " Suren Baghdasaryan
2024-03-27  4:30 ` [PATCH 0/6] Documentation fixes for memory allocation profiling Randy Dunlap

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=20240326231453.1206227-1-surenb@google.com \
    --to=surenb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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