From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org, rppt@kernel.org,
axelrasmussen@google.com, lkp@intel.com,
akpm@linux-foundation.org
Subject: [folded-merged] mm-secretmem-fix-panic-when-growing-a-memfd_secret-fix.patch removed from -mm tree
Date: Thu, 14 Apr 2022 18:57:34 -0700 [thread overview]
Message-ID: <20220415015735.7F1BBC385A5@smtp.kernel.org> (raw)
The patch titled
Subject: mm/secretmem: secretmem_iops can be static
has been removed from the -mm tree. Its filename was
mm-secretmem-fix-panic-when-growing-a-memfd_secret-fix.patch
This patch was dropped because it was folded into mm-secretmem-fix-panic-when-growing-a-memfd_secret.patch
------------------------------------------------------
From: kernel test robot <lkp@intel.com>
Subject: mm/secretmem: secretmem_iops can be static
mm/secretmem.c:173:31: warning: symbol 'secretmem_iops' was not declared. Should it be static?
Link: https://lkml.kernel.org/r/YkXc0RjJYQoGZZ8A@57de4820519d
Fixes: 24209f2f4d62 ("mm/secretmem: fix panic when growing a memfd_secret")
Signed-off-by: kernel test robot <lkp@intel.com>
Reported-by: kernel test robot <lkp@intel.com>
Cc: Axel Rasmussen <axelrasmussen@google.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Mike Rapoport <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/secretmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/secretmem.c~mm-secretmem-fix-panic-when-growing-a-memfd_secret-fix
+++ a/mm/secretmem.c
@@ -170,7 +170,7 @@ static int secretmem_setattr(struct user
return simple_setattr(mnt_userns, dentry, iattr);
}
-const struct inode_operations secretmem_iops = {
+static const struct inode_operations secretmem_iops = {
.setattr = secretmem_setattr,
};
_
Patches currently in -mm which might be from lkp@intel.com are
mm-secretmem-fix-panic-when-growing-a-memfd_secret.patch
mm-shmem-handle-uffd-wp-during-fork-fix.patch
reply other threads:[~2022-04-15 1:57 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=20220415015735.7F1BBC385A5@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox