From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,pratyush@kernel.org,pasha.tatashin@soleen.com,leotimmins1974@gmail.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] liveupdate-initialize-incoming-flb-state-before-finish-fix.patch removed from -mm tree
Date: Fri, 03 Apr 2026 10:19:43 -0700 [thread overview]
Message-ID: <20260403171944.02321C4CEF7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: liveupdate-initialize-incoming-flb-state-before-finish-fix
has been removed from the -mm tree. Its filename was
liveupdate-initialize-incoming-flb-state-before-finish-fix.patch
This patch was dropped because it was folded into liveupdate-initialize-incoming-flb-state-before-finish.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: liveupdate-initialize-incoming-flb-state-before-finish-fix
Date: Fri Mar 27 05:21:05 PM PDT 2026
remove unneeded braces, per Pasha
Cc: Leo Timmins <leotimmins1974@gmail.com>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Pratyush Yadav <pratyush@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/liveupdate/luo_flb.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/kernel/liveupdate/luo_flb.c~liveupdate-initialize-incoming-flb-state-before-finish-fix
+++ a/kernel/liveupdate/luo_flb.c
@@ -210,9 +210,8 @@ static void luo_flb_file_finish_one(stru
}
}
- scoped_guard(mutex, &private->incoming.lock) {
+ scoped_guard(mutex, &private->incoming.lock)
count = --private->incoming.count;
- }
if (!count) {
struct liveupdate_flb_op_args args = {0};
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
liveupdate-initialize-incoming-flb-state-before-finish.patch
reply other threads:[~2026-04-03 17:19 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=20260403171944.02321C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=leotimmins1974@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox