From: Mark Brown <broonie@kernel.org>
To: Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patch in the liveupdate tree
Date: Sun, 26 Jul 2026 22:34:04 +0100 [thread overview]
Message-ID: <amZ9TMnWRcvjlsOH@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
Hi all,
The following commit is also in the liveupdate-fixes tree as a different
commit (but the same patch):
05cf3d87a0bf2 ("liveupdate: reject nonzero reserved value for SESSION_FINISH")
36882f3392395 ("liveupdate: Reference count outgoing FLB data")
5c4a03afcb217 ("liveupdate: Remember FLB retrieve() status")
797fe91e50d69 ("kho: align kho_scratch to MAX_ORDER_NR_PAGES pages")
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-26 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 21:34 Mark Brown [this message]
2026-07-27 5:35 ` linux-next: duplicate patch in the liveupdate tree Mike Rapoport
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=amZ9TMnWRcvjlsOH@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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