All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: lars.kurth@citrix.com, wei.liu2@citrix.com,
	andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, jbeulich@suse.com
Subject: Re: [PATCH 2/2] libacpi: Be specific about which DSDT files to build
Date: Tue, 15 Nov 2016 06:17:28 +0000	[thread overview]
Message-ID: <20161115061728.GR23528@citrix.com> (raw)
In-Reply-To: <1479185547-2873-3-git-send-email-boris.ostrovsky@oracle.com>

On Mon, Nov 14, 2016 at 11:52:27PM -0500, Boris Ostrovsky wrote:
> There is no reason to build, for example, dsdt_pvh.asl for hvmloader. We
> pass which DSDTs to build via DSDT_FILES parameter.
> 
> If DSDT_FILES is empty all DSDTs for a particular architecture will be built.
> 
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

Acked-by: Wei Liu <wei.liu2@citrix.com>

This doesn't seem to be strictly necessary for 4.8 though.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-15  6:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  4:52 [PATCH 0/2] libacpi updates Boris Ostrovsky
2016-11-15  4:52 ` [PATCH 1/2] tools/libacpi: Re-licence remaining GPL code to LGPLv2.1 Boris Ostrovsky
2016-11-15  6:14   ` Wei Liu
2016-11-15  8:10   ` Jan Beulich
2016-11-15 15:14   ` Wei Liu
2016-11-15  4:52 ` [PATCH 2/2] libacpi: Be specific about which DSDT files to build Boris Ostrovsky
2016-11-15  6:17   ` Wei Liu [this message]
2016-11-15 13:35     ` Boris Ostrovsky
2016-11-15 13:45       ` Andrew Cooper
2016-11-15 14:14         ` Lars Kurth
2016-11-15  8:14   ` Jan Beulich
2016-11-15  4:55 ` [PATCH 0/2] libacpi updates Boris Ostrovsky

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=20161115061728.GR23528@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xen.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 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.