All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Vehlow <lkml@jv-coder.de>
To: rpalethorpe@suse.de
Cc: ltp@lists.linux.it, Joerg Vehlow <joerg.vehlow@aox.de>
Subject: Re: [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout
Date: Wed, 27 Jul 2022 07:42:20 +0200	[thread overview]
Message-ID: <cadd0a8c-51a3-0ced-f0d7-eeaf15999f98@jv-coder.de> (raw)
In-Reply-To: <87zghoq9km.fsf@suse.de>

Hi Richard

Am 7/5/2022 um 9:37 AM schrieb Richard Palethorpe:
> Hello Joerg,
> 
> Joerg Vehlow <lkml@jv-coder.de> writes:
> 
> OK, so things are being installed twice and it is generally a
> mess. This looks like a good cleanup.
> 
> However this really needs to be explained in the patchset. There
> needs to be a clear description of where things have moved from and
> to. In particular what someone needs to do if this breaks their test
> runner scripts. This can then be copied into the LTP release notes.

I think this is explained now in v2 in the commit message.

> BTW IIRC we generate runtest files for the open posix tests and the test
> runner handles them almost like normal LTP tests. We don't use any of
> those scripts either.
I was not able to find anything like this.

Joerg

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-07-27  5:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 12:53 [LTP] [0/3] openposix: Fix installation file layout Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 1/3] openposix: Fix existence test for local flag-files Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout Joerg Vehlow
2022-07-05  5:57   ` Richard Palethorpe
2022-07-05  6:28     ` Richard Palethorpe
2022-07-05  6:37       ` Joerg Vehlow
2022-07-05  7:37         ` Richard Palethorpe
2022-07-27  5:42           ` Joerg Vehlow [this message]
2022-07-05  6:43     ` Joerg Vehlow
2022-07-27  5:26     ` Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 3/3] configure: Integrate open posix testsuite configure Joerg Vehlow
2022-07-05  6:22   ` Richard Palethorpe

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=cadd0a8c-51a3-0ced-f0d7-eeaf15999f98@jv-coder.de \
    --to=lkml@jv-coder.de \
    --cc=joerg.vehlow@aox.de \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.de \
    /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.