xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
	xen-devel@lists.xenproject.org
Subject: Re: Build error iasl/dsdt after commit "hvmloader: also cover PCI MMIO ranges above 4G with UC MTRR ranges"
Date: Thu, 22 May 2014 13:21:31 +0100	[thread overview]
Message-ID: <537E07EB0200007800014F24@mail.emea.novell.com> (raw)
In-Reply-To: <1400753577.15916.1.camel@kazak.uk.xensource.com>

>>> On 22.05.14 at 12:12, <Ian.Campbell@eu.citrix.com> wrote:
> On Thu, 2014-05-22 at 11:07 +0100, Jan Beulich wrote:
>> >>> On 22.05.14 at 11:56, <Ian.Campbell@eu.citrix.com> wrote:
>> > Ah yes. this works:
>> >                  QWordMemory (
>> >                          ResourceProducer, PosDecode, MinFixed, MaxFixed,
>> >                          NonCacheable, ReadWrite,
>> >                          0x0000000000000000,
>> >                          0x0000000ffffffff0,
>> >                          0x0000000fffffffff,
>> >                          0x0000000000000000,
>> >                          0x0000000000000010,
>> >                          ,, _Y02)
>> 
>> Good. Are you okay with an incremental fix (once tested), or should
>> I revert?
> 
> Incremental is fine by me. In fact for a patch which changes to the
> above: Acked-by: Ian Campbell <ian.campbell@citrix.com>

Thanks, committed and pushed.

Jan

      reply	other threads:[~2014-05-22 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 18:58 Build error iasl/dsdt after commit "hvmloader: also cover PCI MMIO ranges above 4G with UC MTRR ranges" Sander Eikelenboom
2014-05-22  7:24 ` Jan Beulich
2014-05-22  9:16   ` Ian Campbell
2014-05-22  9:30     ` Jan Beulich
2014-05-22  9:56       ` Ian Campbell
2014-05-22 10:07         ` Jan Beulich
2014-05-22 10:12           ` Ian Campbell
2014-05-22 12:21             ` Jan Beulich [this message]

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=537E07EB0200007800014F24@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).