From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, lkp@intel.com,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
songmuchun@bytedance.com
Subject: [folded-merged] proc-remove-pde_data-completely-fix-fix.patch removed from -mm tree
Date: Fri, 21 Jan 2022 17:22:21 -0800 [thread overview]
Message-ID: <20220122012221.kRWwYhea1%akpm@linux-foundation.org> (raw)
The patch titled
Subject: proc-remove-pde_data-completely-fix-fix
has been removed from the -mm tree. Its filename was
proc-remove-pde_data-completely-fix-fix.patch
This patch was dropped because it was folded into proc-remove-pde_data-completely.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: proc-remove-pde_data-completely-fix-fix
Cc: Muchun Song <songmuchun@bytedance.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/nubus/proc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/nubus/proc.c~proc-remove-pde_data-completely-fix-fix
+++ a/drivers/nubus/proc.c
@@ -93,7 +93,7 @@ struct nubus_proc_pde_data {
static struct nubus_proc_pde_data *
nubus_proc_alloc_pde_data(unsigned char *ptr, unsigned int size)
{
- struct nubus_proc_pded *pded;
+ struct nubus_proc_pde_data *pded;
pded = kmalloc(sizeof(*pded), GFP_KERNEL);
if (!pded)
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
proc-remove-pde_data-completely.patch
mm-remove-cleancache-fix.patch
mm-simplify-try_to_unuse-fix.patch
mm.patch
documentation-vm-page_ownerrst-update-the-documentation-fix.patch
mm-mempolicy-convert-from-atomic_t-to-refcount_t-on-mempolicy-refcnt-fix.patch
arch-x86-include-asm-pgtableh-needs-spinlockh.patch
mutex-subsystem-synchro-test-module-fix.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2022-01-22 1:22 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=20220122012221.kRWwYhea1%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=songmuchun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox