From: Luis Chamberlain <mcgrof@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH kdevops v2 1/4] Kconfig: s/VAGRANT_LIBVIRT/LIBVIRT/
Date: Fri, 8 Dec 2023 18:08:52 -0800 [thread overview]
Message-ID: <ZXPMNPDYc8KIL39p@bombadil.infradead.org> (raw)
In-Reply-To: <ZXPLvqg9FmvNAWmQ@bombadil.infradead.org>
On Fri, Dec 08, 2023 at 06:06:55PM -0800, Luis Chamberlain wrote:
> OK now that I've reviewed the entire patch series I think what is
> missing after this patch, to make things clean is to move all the
> libvirt stuff into its own file, and then leaving in the vagrant
> makefile only things related to vagrant.
Sorry I meant that leaving in the vagrant kconfig file only things
relating to vagrant. This way vagrant libvirt plugin stuff selects
libvirt. And so does libguest.
Luis
next prev parent reply other threads:[~2023-12-09 2:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 15:01 [PATCH kdevops v2 0/4] guestfs: replacement for vagrant in kdevops Jeff Layton
2023-12-08 15:01 ` [PATCH kdevops v2 1/4] Kconfig: s/VAGRANT_LIBVIRT/LIBVIRT/ Jeff Layton
2023-12-09 2:05 ` Luis Chamberlain
2023-12-09 2:06 ` Luis Chamberlain
2023-12-09 2:08 ` Luis Chamberlain [this message]
2023-12-09 12:07 ` Jeff Layton
2023-12-08 15:01 ` [PATCH kdevops v2 2/4] nfsd: key off of LIBVIRT instead of VAGRANT for storage config Jeff Layton
2023-12-08 15:01 ` [PATCH kdevops v2 3/4] vagrant: rename the RHEL registration settings Jeff Layton
2023-12-08 15:23 ` Jeff Layton
2023-12-08 15:01 ` [PATCH kdevops v2 4/4] guestfs: add a new local guest management variant Jeff Layton
2023-12-09 2:14 ` Luis Chamberlain
2023-12-09 12:25 ` Jeff Layton
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=ZXPMNPDYc8KIL39p@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=jlayton@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