From: Andrew Morton <akpm@linux-foundation.org>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Hugh Dickins <hughd@google.com>,
Barry Song <baohua@kernel.org>,
David Hildenbrand <david@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Lance Yang <ioworker0@gmail.com>,
linux-mm@kvack.org, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-dev@igalia.com
Subject: Re: [PATCH v5 0/5] mm: add more kernel parameters to control mTHP
Date: Fri, 1 Nov 2024 11:30:06 -0700 [thread overview]
Message-ID: <20241101113006.454a96eaafc723ebde69429f@linux-foundation.org> (raw)
In-Reply-To: <20241101165719.1074234-2-mcanal@igalia.com>
On Fri, 1 Nov 2024 13:54:04 -0300 Maíra Canal <mcanal@igalia.com> wrote:
> This series introduces four patches related to the kernel parameters
> controlling mTHP and a fifth patch replacing `strcpy()` for `strscpy()`
> in the file `mm/huge_memory.c`.
Thanks. I extracted [1/1] from the series, as the first patch is
6.12-rcX material.
prev parent reply other threads:[~2024-11-01 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 16:54 Maíra Canal
2024-11-01 16:54 ` [PATCH v5 1/5] mm: fix docs for the kernel parameter ``thp_anon=`` Maíra Canal
2024-11-01 16:54 ` [PATCH v5 2/5] mm: shmem: control THP support through the kernel command line Maíra Canal
2024-11-01 16:54 ` [PATCH v5 3/5] mm: move ``get_order_from_str()`` to internal.h Maíra Canal
2024-11-04 2:25 ` Baolin Wang
2024-11-04 11:16 ` Maíra Canal
2024-11-01 16:54 ` [PATCH v5 4/5] mm: shmem: override mTHP shmem default with a kernel parameter Maíra Canal
2024-11-04 2:33 ` Baolin Wang
2024-11-01 16:54 ` [PATCH v5 5/5] mm: huge_memory: Use strscpy() instead of strcpy() Maíra Canal
2024-11-01 18:30 ` Andrew Morton [this message]
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=20241101113006.454a96eaafc723ebde69429f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=kernel-dev@igalia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcanal@igalia.com \
--cc=ryan.roberts@arm.com \
/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