From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
rppt@kernel.org, usama.arif@bytedance.com,
akpm@linux-foundation.org
Subject: [folded-merged] memblock-pass-memblock_type-to-memblock_setclr_flag-fix.patch removed from -mm tree
Date: Wed, 04 Oct 2023 13:17:17 -0700 [thread overview]
Message-ID: <20231004201719.35CF8C433C8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: memblock: add missing argument definition
has been removed from the -mm tree. Its filename was
memblock-pass-memblock_type-to-memblock_setclr_flag-fix.patch
This patch was dropped because it was folded into memblock-pass-memblock_type-to-memblock_setclr_flag.patch
------------------------------------------------------
From: Usama Arif <usama.arif@bytedance.com>
Subject: memblock: add missing argument definition
Date: Mon, 18 Sep 2023 10:06:57 +0100
Description of argument memblock_type was missing in the commit that
introduced it.
Link: https://lkml.kernel.org/r/20230918090657.220463-1-usama.arif@bytedance.com
Fixes: 70083e1c8ab4 ("memblock: pass memblock_type to memblock_setclr_flag")
Signed-off-by: Usama Arif <usama.arif@bytedance.com>
Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memblock.c | 1 +
1 file changed, 1 insertion(+)
--- a/mm/memblock.c~memblock-pass-memblock_type-to-memblock_setclr_flag-fix
+++ a/mm/memblock.c
@@ -892,6 +892,7 @@ int __init_memblock memblock_physmem_add
/**
* memblock_setclr_flag - set or clear flag for a memory region
+ * @type: memblock type to set/clear flag for
* @base: base address of the region
* @size: size of the region
* @set: set or clear the flag
_
Patches currently in -mm which might be from usama.arif@bytedance.com are
mm-hugetlb_vmemmap-use-nid-of-the-head-page-to-reallocate-it.patch
memblock-pass-memblock_type-to-memblock_setclr_flag.patch
memblock-introduce-memblock_rsrv_noinit-flag.patch
mm-hugetlb-skip-initialization-of-gigantic-tail-struct-pages-if-freed-by-hvo.patch
reply other threads:[~2023-10-04 20:17 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=20231004201719.35CF8C433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=usama.arif@bytedance.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 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.