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 updates for 6.2-rc1
Date: Sat, 17 Dec 2022 20:37:30 -0800	[thread overview]
Message-ID: <20221217203730.f48e5345841a57dd6e713faf@linux-foundation.org> (raw)


Linus, please merge this fault-injection patchset.

Thanks.


The following changes since commit 8fa590bf344816c925810331eea8387627bbeb40:

  Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2022-12-15 11:12:21 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-nonmm-stable-2022-12-17-20-32

for you to fetch changes up to f9eeef5918bbe1f2545d36280330dced25d6cf97:

  fault-injection: make stacktrace filter works as expected (2022-12-15 16:40:44 -0800)

----------------------------------------------------------------
Some fault-injection improvements from Wei Yongjun which enable stacktrace
filtering on x86_64.

----------------------------------------------------------------
Wei Yongjun (4):
      fault-injection: allow stacktrace filter for x86-64
      fault-injection: skip stacktrace filtering by default
      fault-injection: make some stack filter attrs more readable
      fault-injection: make stacktrace filter works as expected

 lib/Kconfig.debug  |  1 -
 lib/fault-inject.c | 22 ++++++++++++++--------
 2 files changed, 14 insertions(+), 9 deletions(-)



             reply	other threads:[~2022-12-18  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  4:37 Andrew Morton [this message]
2022-12-19 14:30 ` 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=20221217203730.f48e5345841a57dd6e713faf@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