From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH 0/3] Fixes and workarounds for pasta with Podman in Google Cloud
Date: Thu, 3 Nov 2022 07:36:32 +0100 [thread overview]
Message-ID: <20221103073632.4214ceff@elisabeth> (raw)
In-Reply-To: <Y2Mx4+KiJXk2QzrK@yekko>
On Thu, 3 Nov 2022 14:13:39 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Thu, Nov 03, 2022 at 12:04:40AM +0100, Stefano Brivio wrote:
> > These patches work around or fix some issues found while testing the
> > Podman integration for pasta in Google Compute Engine environments.
>
> Drat. These will conflict pretty badly with the IPv4 address endian
> fixes I just posted.
Not a big issue, I just rebased on top of it.
--
Stefano
prev parent reply other threads:[~2022-11-03 6:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 23:04 [PATCH 0/3] Fixes and workarounds for pasta with Podman in Google Cloud Stefano Brivio
2022-11-02 23:04 ` [PATCH 1/3] conf: Consistency check between configured IPv4 netmask and gateway Stefano Brivio
2022-11-03 3:17 ` David Gibson
2022-11-03 6:39 ` Stefano Brivio
2022-11-02 23:04 ` [PATCH 2/3] conf: Split the notions of read DNS addresses and offered ones Stefano Brivio
2022-11-03 3:37 ` David Gibson
2022-11-03 6:42 ` Stefano Brivio
2022-11-02 23:04 ` [PATCH 3/3] udp: Check for answers to forwarded DNS queries before handling local redirects Stefano Brivio
2022-11-03 3:42 ` David Gibson
2022-11-03 6:42 ` Stefano Brivio
2022-11-05 1:19 ` David Gibson
2022-11-06 22:22 ` Stefano Brivio
2022-11-07 1:08 ` David Gibson
2022-11-07 9:51 ` Stefano Brivio
2022-11-08 5:51 ` David Gibson
2022-11-08 6:22 ` Stefano Brivio
2022-11-10 4:30 ` David Gibson
2022-11-03 3:13 ` [PATCH 0/3] Fixes and workarounds for pasta with Podman in Google Cloud David Gibson
2022-11-03 6:36 ` 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=20221103073632.4214ceff@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.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.
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).