From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev
Subject: Re: [PATCH 0/8] guestfs: fixes and enhancements
Date: Fri, 8 Mar 2024 01:55:45 -0800 [thread overview]
Message-ID: <ZergoTYIEATUbZ42@bombadil.infradead.org> (raw)
In-Reply-To: <20240308000400.1646823-1-mcgrof@kernel.org>
On Thu, Mar 07, 2024 at 04:03:51PM -0800, Luis Chamberlain wrote:
> guestfs didn't work with multiple guests for me and it took me a while
> to figure out why. The issue was a stupid bug where if you have the
> ssh include directive without a new line it won't be processed. So the
> last patch fixes that.
>
> The rest is general cleanup and sanity stuff.
>
> I tested with vagrant too to ensure the Kconfig changes don't break it.
>
> I'd like to wait to push until this is also tesed on aarch64 guests
I didn't wait and pushed but I was confident it wouldn't break aarch64.
Luis
next prev parent reply other threads:[~2024-03-08 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 0:03 [PATCH 0/8] guestfs: fixes and enhancements Luis Chamberlain
2024-03-08 0:03 ` [PATCH 1/8] guestfs: use macros for drives for aarch64 Luis Chamberlain
2024-03-08 0:03 ` [PATCH 2/8] bringup: disable ZNS and CXL for guestfs Luis Chamberlain
2024-03-08 0:03 ` [PATCH 3/8] libvirt: move zns, largio and cxl to its own files Luis Chamberlain
2024-03-08 0:03 ` [PATCH 4/8] guestfs: move options to its own file Luis Chamberlain
2024-03-08 0:03 ` [PATCH 5/8] bringup: match default distro to user's distro Luis Chamberlain
2024-03-08 0:03 ` [PATCH 6/8] guestfs: remove explicit tap0 device name Luis Chamberlain
2024-03-08 0:03 ` [PATCH 7/8] destroy_guestfs.sh: remove known ssh key Luis Chamberlain
2024-03-08 0:03 ` [PATCH 8/8] guestfs: verify new line on ssh include directive Luis Chamberlain
2024-03-08 9:55 ` Luis Chamberlain [this message]
2024-03-08 14:14 ` [PATCH 0/8] guestfs: fixes and enhancements Chuck Lever III
2024-03-08 14:26 ` Chuck Lever III
2024-03-08 15:44 ` Luis Chamberlain
2024-03-08 15:46 ` Chuck Lever III
2024-03-08 15:56 ` Luis Chamberlain
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=ZergoTYIEATUbZ42@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=kdevops@lists.linux.dev \
/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