All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,kaushlendra.kumar@intel.com,akpm@linux-foundation.org
Subject: [folded-merged] tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary-v4.patch removed from -mm tree
Date: Sun, 21 Sep 2025 12:52:13 -0700	[thread overview]
Message-ID: <20250921195213.F0DF3C4CEE7@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary-v4
has been removed from the -mm tree.  Its filename was
     tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary-v4.patch

This patch was dropped because it was folded into tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary.patch

------------------------------------------------------
From: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
Subject: tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary-v4
Date: Mon, 1 Sep 2025 10:19:55 +0530

remove unnecessary blank line

Link: https://lkml.kernel.org/r/20250901044955.3902815-1-kaushlendra.kumar@intel.com
Signed-off-by: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 tools/mm/slabinfo.c |    1 -
 1 file changed, 1 deletion(-)

--- a/tools/mm/slabinfo.c~tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary-v4
+++ a/tools/mm/slabinfo.c
@@ -156,7 +156,6 @@ static void usage(void)
 static unsigned long read_obj(const char *name)
 {
 	size_t len;
-
 	FILE *f = fopen(name, "r");
 
 	if (!f) {
_

Patches currently in -mm which might be from kaushlendra.kumar@intel.com are

tools-mm-slabinfo-fix-access-to-null-terminator-in-string-boundary.patch


                 reply	other threads:[~2025-09-21 19:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250921195213.F0DF3C4CEE7@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=kaushlendra.kumar@intel.com \
    --cc=mm-commits@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.