From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu: Upgrade to 2.8.1.1
Date: Mon, 15 May 2017 21:51:06 +0200 [thread overview]
Message-ID: <1494877866.1179.266.camel@intel.com> (raw)
In-Reply-To: <CAMKF1srM6+insBEWhz2cZXMQyU-n+Qj5esoPx1GfEWB2We-y2g@mail.gmail.com>
On Mon, 2017-05-15 at 08:47 -0700, Khem Raj wrote:
> On Mon, May 15, 2017 at 7:41 AM, Aníbal Limón
> <anibal.limon@linux.intel.com> wrote:
> >> Upstream is already at 2.9, why this version?
> >
> > Patrick has a patches for enable TPM into QEMU 2.8.x line, but there
> > apply into 2.9.x but the compile fails.
> >
> > I guess there's a need to work on those patches before 2.9.x upgrade.
> >
>
> its also easier to backport it to pyro since its fresh release. Eventually yes
> 2.9 is going to come into master.
We are working on better patches for qemu master which make swtpm usable
without being root. Those are under review on the qemu mailing list at
the moment.
The part of the code which gets touched by these patches hasn't changed
much. It shouldn't be hard port either the current patches or the new
ones, should that become necessary for 2.9.x.
--
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-05-15 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 16:49 [PATCH] qemu: Upgrade to 2.8.1.1 Aníbal Limón
2017-05-15 10:49 ` Alexander Kanavin
2017-05-15 14:41 ` Aníbal Limón
2017-05-15 15:47 ` Khem Raj
2017-05-15 19:51 ` 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=1494877866.1179.266.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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