All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ani Sinha <ani@anisinha.ca>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"John Snow" <jsnow@redhat.com>,
	"Maydell Peter" <peter.maydell@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Qemu Devel" <qemu-devel@nongnu.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH v6 00/10] Introduce new acpi/smbios avocado tests using biosbits
Date: Fri, 21 Oct 2022 17:03:00 +0100	[thread overview]
Message-ID: <87lep95ffx.fsf@linaro.org> (raw)
In-Reply-To: <CAARzgwya9jw3YmAwHcSbzzTUewFcq8JR_hVM+=-cSePfyxO1CQ@mail.gmail.com>


Ani Sinha <ani@anisinha.ca> writes:

<snip>
>
>  We have added a mirror of biosbits to the QEMU project so there is no
>  reason why we can't track changes and modifications there (we do this
>  for TestFloat which is forked from the upstream SoftFloat code).
>
> The whole idea was that say an acpi developer added support for a new table in QEMU, he should write a corresponding
> test for bits so that the same table is exercised during run time. Making those changes from a single repo (either directly
> or through a submodule)  makes things lit simpler and also keeps things in sync with each other. If we use separate
> repos for acpi bits test, it will be another mess when comes to developers adding changes and keeping things in sync. 
>
> Anyways these things should have been brought up earlier. I'm out of the debate. 
>
> I've sent v7 , incremental work over the last 6 months in my spare time without getting any pay. So take it or scrap it. 
>
> 😊

I'm sorry you feel that way but you asked for people to spend their time
reviewing your code and giving feedback. If you don't have time to take
it forward then fine but I'm afraid a "take it or leave it" attitude
will just result in it not getting merged.

Hopefully someone else who has the time to look into it will be able to
pick it up later.

-- 
Alex Bennée


  parent reply	other threads:[~2022-10-21 18:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 12:34 [PATCH v6 00/10] Introduce new acpi/smbios avocado tests using biosbits Ani Sinha
2022-10-20 12:34 ` [PATCH v6 01/10] acpi/tests/avocado/bits: initial commit of test scripts that are run by biosbits Ani Sinha
2022-10-20 17:27   ` Alex Bennée
2022-10-20 12:34 ` [PATCH v6 02/10] acpi/tests/avocado/bits: add SPDX license identifiers for bios bits tests Ani Sinha
2022-10-20 12:34 ` [PATCH v6 03/10] acpi/tests/avocado/bits: disable acpi PSS tests that are failing in biosbits Ani Sinha
2022-10-20 17:27   ` Alex Bennée
2022-10-20 12:35 ` [PATCH v6 04/10] acpi/tests/avocado/bits: add smilatency test suite from bits in order to disable it Ani Sinha
2022-10-20 12:35 ` [PATCH v6 05/10] acpi/tests/avocado/bits: add SPDX license identifiers for bios bits smilatency tests Ani Sinha
2022-10-20 17:43   ` Alex Bennée
2022-10-20 12:35 ` [PATCH v6 06/10] acpi/tests/avocado/bits: disable smilatency test since it does not pass everytime Ani Sinha
2022-10-20 17:46   ` Alex Bennée
2022-10-21  8:39     ` Ani Sinha
2022-10-20 12:35 ` [PATCH v6 07/10] acpi/tests/avocado/bits: add biosbits config file for running bios tests Ani Sinha
2022-10-20 17:47   ` Alex Bennée
2022-10-21  5:37     ` Ani Sinha
2022-10-20 12:35 ` [PATCH v6 08/10] acpi/tests/avocado/bits: add acpi and smbios avocado tests that uses biosbits Ani Sinha
2022-10-20 17:30   ` Alex Bennée
2022-10-20 12:35 ` [PATCH v6 09/10] acpi/tests/avocado/bits/doc: add a doc file to describe the acpi bits test Ani Sinha
2022-10-20 17:08   ` Alex Bennée
2022-10-20 12:35 ` [PATCH v6 10/10] MAINTAINERS: add myself as the maintainer for acpi biosbits avocado tests Ani Sinha
2022-10-20 12:38 ` [PATCH v6 00/10] Introduce new acpi/smbios avocado tests using biosbits Michael S. Tsirkin
2022-10-20 12:42   ` Ani Sinha
2022-10-20 12:45     ` Michael S. Tsirkin
2022-10-20 12:50       ` Ani Sinha
2022-10-20 19:13         ` Michael S. Tsirkin
2022-10-20 23:40           ` Ani Sinha
2022-10-21  0:15             ` Ani Sinha
2022-10-21  8:32               ` Michael S. Tsirkin
2022-10-21  8:43                 ` Ani Sinha
2022-10-21  9:30                   ` Alex Bennée
2022-10-21  9:40                     ` Michael S. Tsirkin
2022-10-21  9:58                       ` Ani Sinha
2022-10-21 11:52                         ` Alex Bennée
2022-10-21 12:22                           ` Ani Sinha
2022-10-21 13:13                             ` Ani Sinha
2022-10-21 15:53                               ` Alex Bennée
2022-10-21 16:11                                 ` Ani Sinha
2022-10-22  0:58                                 ` Ani Sinha
2022-10-22 16:35                                   ` Michael S. Tsirkin
2022-10-22 16:43                                     ` Ani Sinha
2022-10-22 16:47                                       ` Michael S. Tsirkin
2022-10-22 10:56                                 ` Ani Sinha
2022-10-21 16:03                             ` Alex Bennée [this message]
2022-10-21 16:17                               ` Ani Sinha
2022-10-22 16:45                                 ` Michael S. Tsirkin
2022-10-22 17:34                                   ` Ani Sinha
2022-10-21  8:20             ` Michael S. Tsirkin
2022-10-21 11:42               ` Ani Sinha
2022-10-22 16:40                 ` Michael S. Tsirkin
2022-10-22 16:44                   ` Ani Sinha

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=87lep95ffx.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=ani@anisinha.ca \
    --cc=berrange@redhat.com \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=imammedo@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.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 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.