qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, pingfank@linux.vnet.ibm.com,
	ehabkost@redhat.com, jordan.l.justen@intel.com,
	coreyb@linux.vnet.ibm.com, qemu-devel <qemu-devel@nongnu.org>,
	pavel.borzenkov@gmail.com, mdroth@linux.vnet.ibm.com,
	zanghongyong@huawei.com, smizrahi@redhat.com,
	hpoussin@reactos.org, pbonzini@redhat.com, mlspirat42@gmail.com,
	david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] Summary of Anthony's 'next' queue
Date: Tue, 15 Nov 2011 07:37:52 -0600	[thread overview]
Message-ID: <4EC26B30.5010506@codemonkey.ws> (raw)
In-Reply-To: <4EC1DDA9.80603@linux.vnet.ibm.com>

On 11/14/2011 09:34 PM, Stefan Berger wrote:
> On 11/14/2011 03:17 PM, Anthony Liguori wrote:
>> Hi,
>>
>> This is a summary of the patches that I have queued in my next tree that were
>> identified as 1.1 candidates. These patches will not be applied until after
>> the 1.1 tree opens (December 1st).
>>
>> These patches have not been tested yet and may receive additional review
>> comments. This note is meant to let submitters know that their patch has not
>> been forgotten.
>>
>> Here's the full list:
>>
>> 050 stefanb@linux.vnet.ibm.com Support for TPM command line options
>> 051 stefanb@linux.vnet.ibm.com Add TPM (frontend) hardware interface (TPM TIS)
>> to Qemu
>> 052 stefanb@linux.vnet.ibm.com Add a debug register
>> 053 stefanb@linux.vnet.ibm.com Build the TPM frontend code
>> 054 stefanb@linux.vnet.ibm.com Add a TPM Passthrough backend driver
>> implementation
>> 055 stefanb@linux.vnet.ibm.com Introduce --enable-tpm-passthrough configure
>> option
>> 056 stefanb@linux.vnet.ibm.com Move parsing of filedescriptor into common
>> function
>> 057 stefanb@linux.vnet.ibm.com Add fd parameter for TPM passthrough driver
>
> I have two patches that fix a deallocation issue in an error path and that
> restrict the 'fd' passed via command line to only be of chardev type. Should I
> post it 'now' or only once 1.1 opens?

I would suggest sending them out in case anyone is interested.  Personally, I'm 
focusing on release issues at the moment so I won't look at them for a couple 
more weeks.

Regards,

Anthony Liguori

>
> Stefan
>

  reply	other threads:[~2011-11-15 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 20:17 [Qemu-devel] Summary of Anthony's 'next' queue Anthony Liguori
2011-11-15  3:34 ` Stefan Berger
2011-11-15 13:37   ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-07 14:37 Anthony Liguori
2012-01-16 15:23 ` Igor Mammedov

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=4EC26B30.5010506@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=hpoussin@reactos.org \
    --cc=jordan.l.justen@intel.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mlspirat42@gmail.com \
    --cc=pavel.borzenkov@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pingfank@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=smizrahi@redhat.com \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=zanghongyong@huawei.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;
as well as URLs for NNTP newsgroup(s).