On Fri, 25 Jan 2019 14:49:28 -0500
"Michael S. Tsirkin" wrote:
> On Fri, Jan 25, 2019 at 09:26:05AM +0100, Igor Mammedov wrote:
> > On Wed, 23 Jan 2019 18:28:59 +
> > "Dr. David Alan Gilbert" wrote:
> >
> > > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > > On Tue, Jan 22, 2019 at
On Fri, Jan 25, 2019 at 09:26:05AM +0100, Igor Mammedov wrote:
> On Wed, 23 Jan 2019 18:28:59 +
> "Dr. David Alan Gilbert" wrote:
>
> > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > On Tue, Jan 22, 2019 at 08:07:41PM +, Dr. David Alan Gilbert wrote:
> > > > Hi,
> > > > I noticed
* Igor Mammedov (imamm...@redhat.com) wrote:
> On Wed, 23 Jan 2019 18:28:59 +
> "Dr. David Alan Gilbert" wrote:
>
> > * Michael S. Tsirkin (m...@redhat.com) wrote:
> > > On Tue, Jan 22, 2019 at 08:07:41PM +, Dr. David Alan Gilbert wrote:
> > > > Hi,
> > > > I noticed that the acpi_1_c
On Wed, 23 Jan 2019 18:28:59 +
"Dr. David Alan Gilbert" wrote:
> * Michael S. Tsirkin (m...@redhat.com) wrote:
> > On Tue, Jan 22, 2019 at 08:07:41PM +, Dr. David Alan Gilbert wrote:
> > > Hi,
> > > I noticed that the acpi_1_compatible flag was misspelt as
> > > a
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Tue, Jan 22, 2019 at 08:07:41PM +, Dr. David Alan Gilbert wrote:
> > Hi,
> > I noticed that the acpi_1_compatible flag was misspelt as
> > apci_1_compatible
> >
> > so have a trivial patch to fix that, but looking at it
On Tue, Jan 22, 2019 at 08:07:41PM +, Dr. David Alan Gilbert wrote:
> Hi,
> I noticed that the acpi_1_compatible flag was misspelt as
> apci_1_compatible
>
> so have a trivial patch to fix that, but looking at it - are
> thre any cases where a[cp]i_1_compatible can possi
Hi,
I noticed that the acpi_1_compatible flag was misspelt as
apci_1_compatible
so have a trivial patch to fix that, but looking at it - are
thre any cases where a[cp]i_1_compatible can possibly be false?
Dave
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK