linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] final non-MM work for 5.19-rc1
Date: Sun, 5 Jun 2022 11:38:00 -0700	[thread overview]
Message-ID: <20220605113800.83dfb5ac57ba1f0f64552d9f@linux-foundation.org> (raw)

Linus,

just a single patch here - to add an arguably missing feature in the
delay accounting code.

The following changes since commit 54eb8462f21fb170a05ad64620f0d8d0cf2b7fb5:

  Merge tag 'rtc-5.19' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux (2022-06-01 14:48:13 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-nonmm-stable-2022-06-05

for you to fetch changes up to 662ce1dc9caf493c309200edbe38d186f1ea20d0:

  delayacct: track delays from write-protect copy (2022-06-01 15:55:25 -0700)

----------------------------------------------------------------
A single featurelet for delay accounting.  Delayed a bit
because, unusually, it had dependencies on both the mm-stable and
mm-nonmm-stable queues.

----------------------------------------------------------------
Yang Yang (1):
      delayacct: track delays from write-protect copy

 Documentation/accounting/delay-accounting.rst |  5 ++++-
 include/linux/delayacct.h                     | 28 +++++++++++++++++++++++++++
 include/uapi/linux/taskstats.h                |  6 +++++-
 kernel/delayacct.c                            | 16 +++++++++++++++
 mm/hugetlb.c                                  |  8 ++++++++
 mm/memory.c                                   |  8 ++++++++
 tools/accounting/getdelays.c                  |  8 +++++++-
 7 files changed, 76 insertions(+), 3 deletions(-)



             reply	other threads:[~2022-06-05 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 18:38 Andrew Morton [this message]
2022-06-06  0:23 ` pr-tracker-bot

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=20220605113800.83dfb5ac57ba1f0f64552d9f@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.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