On Mon, May 13, 2024 at 4:32 PM Michael S. Tsirkin <m...@redhat.com> wrote: > > On Mon, May 13, 2024 at 01:55:50PM +1000, Alistair Francis wrote: > > On Tue, May 7, 2024 at 3:24 PM Sia Jee Heng > > <jeeheng....@starfivetech.com> wrote: > > > > Can you describe why you are doing this and that it will be reverted > > in the commit message? > > > > Alistair > > What motivation are you asking? This follows the normal acpi test update > procedure.
I find it clearer to have commits describe that they are disabling tests for a specific reason. That way it's easier to track what's going on. If ACPI test updates don't usually do that then that's fine with me Alistair > > > > > > > Signed-off-by: Sia Jee Heng <jeeheng....@starfivetech.com> > > > --- > > > tests/qtest/bios-tables-test-allowed-diff.h | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/tests/qtest/bios-tables-test-allowed-diff.h > > > b/tests/qtest/bios-tables-test-allowed-diff.h > > > index dfb8523c8b..3f12ca546b 100644 > > > --- a/tests/qtest/bios-tables-test-allowed-diff.h > > > +++ b/tests/qtest/bios-tables-test-allowed-diff.h > > > @@ -1 +1,3 @@ > > > /* List of comma-separated changed AML files to ignore */ > > > +"tests/data/acpi/virt/riscv64/SPCR", > > > +"tests/data/acpi/virt/aarch64/SPCR", > > > -- > > > 2.34.1 > > > > > > >
