From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/5] RFC: Stub dynamic update implementation
Date: Tue, 17 Mar 2026 01:02:42 +0100 (CET) [thread overview]
Message-ID: <20260317010241.0f817e96@elisabeth> (raw)
In-Reply-To: <20260316054629.239002-1-david@gibson.dropbear.id.au>
On Mon, 16 Mar 2026 16:46:24 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> I've taken Stefano's draft implementation of dynamic updates, and
> polished it up to have a stub implementation of the dynamic update
> protocol. So far it doesn't actually do anything, beyond establishing
> the connection and checking versions. I'm continuing to work on the
> actual guts of it.
>
> Patches 1..3/5 are trivial cleanups I happened across while working on
> this. Feel free to apply if you like. 4/5 clears up a more specific
> problem that caused problems sharing code between client and server.
> 5/5 is the implementation proper.
Applied up to 3/5. Any other reason not to apply 4/5 other than
possibly my pending comment? I'd be happy to keep this series as small
as possible.
--
Stefano
prev parent reply other threads:[~2026-03-17 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 5:46 David Gibson
2026-03-16 5:46 ` [PATCH 1/5] Makefile: Use $^ to avoid duplication in static checker rules David Gibson
2026-03-16 5:46 ` [PATCH 2/5] doc: Fix formatting of (DEPRECATED) notes in man page David Gibson
2026-03-16 5:46 ` [PATCH 3/5] pif: Remove unused PIF_NAMELEN David Gibson
2026-03-16 5:46 ` [PATCH 4/5] treewide: Spell ASSERT() as assert() David Gibson
2026-03-17 0:02 ` Stefano Brivio
2026-03-17 0:39 ` David Gibson
2026-03-17 9:36 ` Stefano Brivio
2026-03-16 5:46 ` [PATCH 5/5] pesto: Introduce stub configuration interface and tool David Gibson
2026-03-17 0:02 ` Stefano Brivio
2026-03-17 0:48 ` David Gibson
2026-03-17 9:36 ` Stefano Brivio
2026-03-17 0:02 ` Stefano Brivio [this message]
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=20260317010241.0f817e96@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).