qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL v3 00/14] acpi, pc, pci, virtio, memory bug fixes


From: Michael S. Tsirkin
Subject: Re: [Qemu-devel] [PULL v3 00/14] acpi, pc, pci, virtio, memory bug fixes
Date: Tue, 11 Mar 2014 13:22:42 +0200

On Tue, Mar 11, 2014 at 10:55:17AM +0000, Peter Maydell wrote:
> On 10 March 2014 19:05, Michael S. Tsirkin <address@hidden> wrote:
> > On Mon, Mar 10, 2014 at 03:38:11PM +0000, Peter Maydell wrote:
> >> On 9 March 2014 19:19, Michael S. Tsirkin <address@hidden> wrote:
> >> > Changes from v2:
> >> >     fix for OSx by Gabriel
> >> >     fixed build on systems without IASL
> >> >
> >> > The following changes since commit 
> >> > f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71:
> >> >
> >> >   Merge remote-tracking branch 'remotes/kvaneesh/for-upstream' into 
> >> > staging (2014-03-08 12:38:43 +0000)
> >> >
> >> > are available in the git repository at:
> >> >
> >> >
> >> >   git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
> >> >
> >> > for you to fetch changes up to 220c8ed536491315b4040d820328b8dfd60d67a7:
> >> >
> >> >   qemu: x86: ignore ioapic polarity (2014-03-09 21:09:38 +0200)
> >>
> >> To follow up on our IRC conversation, I'll apply this
> >> if you can confirm that the new make-check warning messages
> >>
> >> acpi-test: Warning! SSDT mismatch. Actual [asl:/tmp/asl-03GECX.dsl,
> >> aml:/tmp/aml-WK6DCX], Expected [asl:/tmp/asl-HPXDCX.dsl,
> >> aml:tests/acpi-test-data/pc/SSDT].
> >> acpi-test: Warning! SSDT mismatch. Actual [asl:/tmp/asl-KEFJCX.dsl,
> >> aml:/tmp/aml-3EGKCX], Expected [asl:/tmp/asl-4NJJCX.dsl,
> >> aml:tests/acpi-test-data/q35/SSDT].
> >>
> >> are harmless.
> >>
> >> thanks
> >> -- PMM
> >
> > I verified that they are harmless.
> > Not sure how did this creep in, I will fix it in the next PULL.
> 
> Applied to master, thanks.
> 
> -- PMM

BTW I still see these warnings in the logs:
    # gpg: WARNING: This key is not certified with a trusted signature!
    # gpg:          There is no indication that the signature belongs to
    # the 

These seem counter-productive: people get used
to ignoring the warnings.
A bunch of people verified my key at the latest KVM forum
so how about importing keys from contributors
and denying pulls where keys don't match?

-- 
MST



reply via email to

[Prev in Thread] Current Thread [Next in Thread]