From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, wangkefeng.wang@huawei.com,
patrick.wang.shcn@gmail.com, liushixin2@huawei.com,
catalin.marinas@arm.com, akpm@linux-foundation.org,
akpm@linux-foundation.org
Subject: [folded-merged] mm-kmemleak-split-__create_object-into-two-functions-checkpatch-fixes.patch removed from -mm tree
Date: Wed, 25 Oct 2023 16:36:58 -0700 [thread overview]
Message-ID: <20231025233659.6CF56C433C8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-kmemleak-split-__create_object-into-two-functions-checkpatch-fixes
has been removed from the -mm tree. Its filename was
mm-kmemleak-split-__create_object-into-two-functions-checkpatch-fixes.patch
This patch was dropped because it was folded into mm-kmemleak-split-__create_object-into-two-functions.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-kmemleak-split-__create_object-into-two-functions-checkpatch-fixes
Date: Wed Oct 18 08:40:15 AM PDT 2023
ERROR: "foo * bar" should be "foo *bar"
#39: FILE: mm/kmemleak.c:626:
+static struct kmemleak_object * __alloc_object(gfp_t gfp)
total: 1 errors, 0 warnings, 99 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
./patches/mm-kmemleak-split-__create_object-into-two-functions.patch has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Please run checkpatch prior to sending patches
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Liu Shixin <liushixin2@huawei.com>
Cc: Patrick Wang <patrick.wang.shcn@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/kmemleak.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/kmemleak.c~mm-kmemleak-split-__create_object-into-two-functions-checkpatch-fixes
+++ a/mm/kmemleak.c
@@ -623,7 +623,7 @@ static noinline depot_stack_handle_t set
return trace_handle;
}
-static struct kmemleak_object * __alloc_object(gfp_t gfp)
+static struct kmemleak_object *__alloc_object(gfp_t gfp)
{
struct kmemleak_object *object;
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-shmem-fix-race-in-shmem_undo_range-w-thp-fix.patch
mm-kmemleak-split-__create_object-into-two-functions.patch
mm-migrate-add-nr_split-to-trace_mm_migrate_pages-stats-fix.patch
reply other threads:[~2023-10-25 23:37 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=20231025233659.6CF56C433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=mm-commits@vger.kernel.org \
--cc=patrick.wang.shcn@gmail.com \
--cc=wangkefeng.wang@huawei.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.