From: Patrick Ohly <patrick.ohly@intel.com>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] flex: upgrade to 2.6.2
Date: Fri, 20 Jan 2017 14:37:10 +0100 [thread overview]
Message-ID: <1484919430.23233.118.camel@intel.com> (raw)
In-Reply-To: <1484846629.23233.83.camel@intel.com>
On Thu, 2017-01-19 at 18:23 +0100, Patrick Ohly wrote:
> Perhaps someone with more knowledge about flex can provide some
> guidance?
>
> Fathi, is that something that you or upstream have come across?
After looking into this some more I've come to the conclusion that this
looks like a bug in flex, so I have filed
https://github.com/westes/flex/issues/164
I also have a workaround for acpica, which I am going to add to V3 of
the UEFI/OVMF patch series.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-01-20 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 15:59 [PATCH] flex: upgrade to 2.6.2 Ross Burton
2017-01-19 17:23 ` Patrick Ohly
2017-01-20 13:37 ` Patrick Ohly [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=1484919430.23233.118.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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