From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, joe@perches.com, masahiroy@kernel.org,
mm-commits@vger.kernel.org, wanjiabing@vivo.com
Subject: [folded-merged] scripts-a-new-script-for-checking-duplicate-struct-declaration-fix.patch removed from -mm tree
Date: Thu, 29 Apr 2021 22:20:23 -0700 [thread overview]
Message-ID: <20210430052023.7PSo5QUMs%akpm@linux-foundation.org> (raw)
The patch titled
Subject: scripts-a-new-script-for-checking-duplicate-struct-declaration-fix
has been removed from the -mm tree. Its filename was
scripts-a-new-script-for-checking-duplicate-struct-declaration-fix.patch
This patch was dropped because it was folded into scripts-a-new-script-for-checking-duplicate-struct-declaration.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: scripts-a-new-script-for-checking-duplicate-struct-declaration-fix
fix usage message, grammar
Cc: Joe Perches <joe@perches.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Wan Jiabing <wanjiabing@vivo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
scripts/checkdeclares.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/scripts/checkdeclares.pl~scripts-a-new-script-for-checking-duplicate-struct-declaration-fix
+++ a/scripts/checkdeclares.pl
@@ -15,8 +15,8 @@
use strict;
sub usage {
- print "Usage: checkdeclares.pl \n";
- print "We just warn of struct declaration duplicates\n";
+ print "Usage: checkdeclares.pl file1.h ...\n";
+ print "Warns of struct declaration duplicates\n";
exit 1;
}
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
scripts-a-new-script-for-checking-duplicate-struct-declaration.patch
mm-memcontrol-switch-to-rstat-fix.patch
mm-vmalloc-remove-unmap_kernel_range-fix-fix.patch
mm-page_alloc-add-an-array-based-interface-to-the-bulk-page-allocator-fix.patch
mm.patch
mm-vmscan-add-shrinker_info_protected-helper-fix.patch
mm-drop-redundant-arch_enable__migration-fix.patch
mm-drop-redundant-arch_enable__migration-fix-fix.patch
kernel-resource-allow-region_intersects-users-to-hold-resource_lock-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
cifsd-is-broken.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2021-04-30 5:20 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=20210430052023.7PSo5QUMs%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=wanjiabing@vivo.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;
as well as URLs for NNTP newsgroup(s).