From: Luiz Capitulino <luizcap@redhat.com>
To: catalin.marinas@arm.com
Cc: lcapitulino@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, david@redhat.com
Subject: [PATCH 0/3] mm: kmemleak: small cleanup
Date: Wed, 30 Apr 2025 16:59:44 -0400 [thread overview]
Message-ID: <cover.1746046744.git.luizcap@redhat.com> (raw)
Hi,
This is a trivial mm/kmemleak.c cleanup. I found these while reading through
the code.
Luiz Capitulino (3):
mm: kmemleak: drop kmemleak_warning variable
mm: kmemleak: drop wrong comment
mm: kmemleak: mark variables as __read_mostly
mm/kmemleak.c | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-30 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:59 Luiz Capitulino [this message]
2025-04-30 20:59 ` [PATCH 1/3] mm: kmemleak: drop kmemleak_warning variable Luiz Capitulino
2025-05-01 10:39 ` Catalin Marinas
2025-04-30 20:59 ` [PATCH 2/3] mm: kmemleak: drop wrong comment Luiz Capitulino
2025-05-01 10:40 ` Catalin Marinas
2025-04-30 20:59 ` [PATCH 3/3] mm: kmemleak: mark variables as __read_mostly Luiz Capitulino
2025-05-01 10:42 ` Catalin Marinas
2025-04-30 21:06 ` [PATCH 0/3] mm: kmemleak: small cleanup David Hildenbrand
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=cover.1746046744.git.luizcap@redhat.com \
--to=luizcap@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=lcapitulino@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.