From: Wei Liu <wei.liu2@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Jan Beulich <JBeulich@suse.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: [PATCH] firmware/rombios: fix after update to libacpi
Date: Tue, 13 Dec 2016 17:47:52 +0000 [thread overview]
Message-ID: <20161213174752.GZ25175@citrix.com> (raw)
In-Reply-To: <20161213171540.3096-1-roger.pau@citrix.com>
On Tue, Dec 13, 2016 at 05:15:40PM +0000, Roger Pau Monne wrote:
> Fix a build breakage after the libacpi changes, this is due to rombios using the
> libacpi headers in order to parse the ACPI tables.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Reported-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Pushed with Andrew's Reviewed-by -- he said LGTM on IRC.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-13 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 17:15 [PATCH] firmware/rombios: fix after update to libacpi Roger Pau Monne
2016-12-13 17:47 ` Wei Liu [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=20161213174752.GZ25175@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=roger.pau@citrix.com \
--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).