From: Andrew Morton <akpm@linux-foundation.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: corbet@lwn.net, nicolas.frattaroli@collabora.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kees@kernel.org, davidgow@google.com, pmladek@suse.com,
tamird@gmail.com, raemoar63@gmail.com, ebiggers@kernel.org,
diego.daniel.professional@gmail.com, rppt@kernel.org,
pratyush@kernel.org, jasonmiu@google.com, graf@amazon.com,
dmatlack@google.com, rientjes@google.com
Subject: Re: [PATCH v1 3/3] liveupdate: luo_file: Use private list
Date: Wed, 17 Dec 2025 14:47:58 -0800 [thread overview]
Message-ID: <20251217144758.4cb7fc20f6fe32a36e8e52ea@linux-foundation.org> (raw)
In-Reply-To: <20251126185725.4164769-4-pasha.tatashin@soleen.com>
On Wed, 26 Nov 2025 13:57:25 -0500 Pasha Tatashin <pasha.tatashin@soleen.com> wrote:
> Switch LUO to use the private list iterators.
Seems kernel/liveupdate/luo_flb.c now needs conversion. Oh well, I'll
await v2.
next prev parent reply other threads:[~2025-12-17 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 18:57 [PATCH v1 0/3] list: add primitives for private list manipulations Pasha Tatashin
2025-11-26 18:57 ` [PATCH v1 1/3] " Pasha Tatashin
2025-11-26 18:57 ` [PATCH v1 2/3] list: add kunit test for private list primitives Pasha Tatashin
2025-11-29 7:47 ` David Gow
2025-11-29 19:48 ` Pasha Tatashin
2025-11-26 18:57 ` [PATCH v1 3/3] liveupdate: luo_file: Use private list Pasha Tatashin
2025-12-17 22:47 ` Andrew Morton [this message]
2025-12-18 0:58 ` Pasha Tatashin
2025-11-26 19:19 ` [PATCH v1 0/3] list: add primitives for private list manipulations Andrew Morton
2025-11-28 14:45 ` Pasha Tatashin
2025-12-06 0:52 ` Pasha Tatashin
2025-12-06 21:39 ` Andrew Morton
2025-12-06 23:25 ` Pasha Tatashin
2025-11-27 5:09 ` 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=20251217144758.4cb7fc20f6fe32a36e8e52ea@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=diego.daniel.professional@gmail.com \
--cc=dmatlack@google.com \
--cc=ebiggers@kernel.org \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=pasha.tatashin@soleen.com \
--cc=pmladek@suse.com \
--cc=pratyush@kernel.org \
--cc=raemoar63@gmail.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=tamird@gmail.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
all inboxes | Powered by JetHome®