linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: David Matlack <dmatlack@google.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	Dave Jiang <dave.jiang@intel.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>
Subject: Re: [PATCH] vfio: selftests: Store libvfio build outputs in $(OUTPUT)/libvfio
Date: Thu, 6 Nov 2025 21:34:22 -0700	[thread overview]
Message-ID: <20251106213422.1632efef.alex@shazbot.org> (raw)
In-Reply-To: <20250922224857.2528737-1-dmatlack@google.com>

On Mon, 22 Sep 2025 22:48:57 +0000
David Matlack <dmatlack@google.com> wrote:

> Store the tools/testing/selftests/vfio/lib outputs (e.g. object files)
> in $(OUTPUT)/libvfio rather than in $(OUTPUT)/lib. This is in
> preparation for building the VFIO selftests library into the KVM
> selftests (see Link below).
> 
> Specifically this will avoid name conflicts between
> tools/testing/selftests/{vfio,kvm/lib and also avoid leaving behind
> empty directories under tools/testing/selftests/kvm after a make clean.
> 
> Link: https://lore.kernel.org/kvm/20250912222525.2515416-2-dmatlack@google.com/
> Signed-off-by: David Matlack <dmatlack@google.com>
> ---
> 
> Note: This patch applies on top of vfio/next.
> 
> https://github.com/awilliam/linux-vfio/tree/next
> 
>  tools/testing/selftests/vfio/lib/libvfio.mk | 20 +++++++++++---------
>  1 file changed, 11 insertions(+), 9 deletions(-)

Applied to vfio next branch for v6.19.  Thanks,

Alex

      reply	other threads:[~2025-11-07  4:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 22:48 [PATCH] vfio: selftests: Store libvfio build outputs in $(OUTPUT)/libvfio David Matlack
2025-11-07  4:34 ` Alex Williamson [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=20251106213422.1632efef.alex@shazbot.org \
    --to=alex@shazbot.org \
    --cc=alex.williamson@redhat.com \
    --cc=dave.jiang@intel.com \
    --cc=dmatlack@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=vinicius.gomes@intel.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;
as well as URLs for NNTP newsgroup(s).