All of lore.kernel.org
 help / color / mirror / Atom feed
From: dmukhin@xen.org
To: Jan Beulich <jbeulich@suse.com>
Cc: andrew.cooper3@citrix.com, anthony.perard@vates.tech,
	julien@xen.org, michal.orzel@amd.com, roger.pau@citrix.com,
	sstabellini@kernel.org, dmukhin@ford.com,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/4] tests: fixup domid make fragment
Date: Thu, 15 Jan 2026 01:01:50 -0800	[thread overview]
Message-ID: <aWis/n2yse0A59+A@kraken> (raw)
In-Reply-To: <2badbc33-f78c-47d9-acef-9383a5aa3387@suse.com>

On Mon, Jan 12, 2026 at 12:16:46PM +0100, Jan Beulich wrote:
> On 11.01.2026 05:11, dmukhin@xen.org wrote:
> > From: Denis Mukhin <dmukhin@ford.com> 
> > 
> > There can be multiple test harnesses per one test target (e.g. harness.h
> > and harness2.h). Account for that by further parametrizing existing
> > emit-harness-nested-rule().
> 
> Multiple harnesses within a single dir imo likely would share headers, but
> use different .c files. Also, why would dependencies on headers need
> recording at all? The Makefile includes $(DEPS_INCLUDE), so all dependency
> concerns should be covered (or else the generic machinery would need
> fixing). Imo all of this wants simplifying (dropping?) rather than further
> complicating.

Whoops, I forgot to drop that multi-harness stuff.
Thanks!

> 
> Jan


  reply	other threads:[~2026-01-15  9:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11  4:11 [PATCH v2 0/4] tools/tests: test harness fragment dmukhin
2026-01-11  4:11 ` [PATCH v2 1/4] tests: fixup domid make fragment dmukhin
2026-01-12 11:16   ` Jan Beulich
2026-01-15  9:01     ` dmukhin [this message]
2026-01-24  0:59   ` Stefano Stabellini
2026-01-11  4:11 ` [PATCH v2 2/4] tests: introduce common fragment for unit tests dmukhin
2026-01-24  1:05   ` Stefano Stabellini
2026-01-11  4:11 ` [PATCH v2 3/4] tests: use unit test fragment in PDX test dmukhin
2026-01-24  1:09   ` Stefano Stabellini
2026-02-06  1:42     ` dmukhin
2026-01-11  4:11 ` [PATCH v2 4/4] tests: use unit test fragment in vPCI test dmukhin
2026-01-24  1:25   ` Stefano Stabellini
2026-02-06  1:47     ` dmukhin

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=aWis/n2yse0A59+A@kraken \
    --to=dmukhin@xen.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=dmukhin@ford.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.