From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,kent.overstreet@linux.dev,akpm@linux-foundation.org
Subject: [folded-merged] fix-missing-vmalloch-includes-fix.patch removed from -mm tree
Date: Thu, 25 Apr 2024 20:05:02 -0700 [thread overview]
Message-ID: <20240426030502.F2FABC113CC@smtp.kernel.org> (raw)
The quilt patch titled
Subject: fixup! fix missing vmalloc.h includes
has been removed from the -mm tree. Its filename was
fix-missing-vmalloch-includes-fix.patch
This patch was dropped because it was folded into fix-missing-vmalloch-includes.patch
------------------------------------------------------
From: Kent Overstreet <kent.overstreet@linux.dev>
Subject: fixup! fix missing vmalloc.h includes
Date: Tue, 26 Mar 2024 20:21:52 -0400
The previous patch added string.h to arch/alpha/lib/memcpy.c to fix a
warning about a missing forward declaration - but this breaks with -
presumably - some fortify source shenanigans that redefine memcpy as a
macro.
Link: https://lkml.kernel.org/r/20240327002152.3339937-1-kent.overstreet@linux.dev
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/alpha/lib/memcpy.c | 1 -
1 file changed, 1 deletion(-)
--- a/arch/alpha/lib/memcpy.c~fix-missing-vmalloch-includes-fix
+++ a/arch/alpha/lib/memcpy.c
@@ -18,7 +18,6 @@
#include <linux/types.h>
#include <linux/export.h>
-#include <linux/string.h>
/*
* This should be done in one go with ldq_u*2/mask/stq_u. Do it
_
Patches currently in -mm which might be from kent.overstreet@linux.dev are
fix-missing-vmalloch-includes.patch
fix-missing-vmalloch-includes-fix-4.patch
asm-generic-ioh-kill-vmalloch-dependency.patch
mm-slub-mark-slab_free_freelist_hook-__always_inline.patch
scripts-kallysms-always-include-__start-and-__stop-symbols.patch
fs-convert-alloc_inode_sb-to-a-macro.patch
rust-add-a-rust-helper-for-krealloc.patch
mempool-hook-up-to-memory-allocation-profiling.patch
mm-percpu-introduce-pcpuobj_ext.patch
mm-percpu-add-codetag-reference-into-pcpuobj_ext.patch
mm-vmalloc-enable-memory-allocation-profiling.patch
rhashtable-plumb-through-alloc-tag.patch
maintainers-add-entries-for-code-tagging-and-memory-allocation-profiling.patch
memprofiling-documentation.patch
reply other threads:[~2024-04-26 3:05 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=20240426030502.F2FABC113CC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--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.