qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, stefanb@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH] tpm: Add missing common TPM SSDT file
Date: Tue, 2 Jun 2015 15:31:48 +0200	[thread overview]
Message-ID: <20150602153044-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <556DAE57.3060606@linux.vnet.ibm.com>

On Tue, Jun 02, 2015 at 09:23:35AM -0400, Stefan Berger wrote:
> On 06/02/2015 09:22 AM, Michael S. Tsirkin wrote:
> >On Tue, Jun 02, 2015 at 09:14:29AM -0400, Stefan Berger wrote:
> >>On 06/02/2015 02:48 AM, Michael S. Tsirkin wrote:
> >>>On Mon, Jun 01, 2015 at 08:32:55PM -0400, Stefan Berger wrote:
> >>>>This patch adds the missing common SSDT TPM file.
> >>>>
> >>>>Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> >>>I posted this too. But we really should just get rid of all this: we
> >>>have already removed most ASL code except for the DSDT.
> >>Yes, I will do that. Though for reviewing I think ASL is still easier to
> >>understand.
> >>
> >>   Stefan
> >A bit, but once you get into more trickery, like you do with ifdefs
> >with QEMU-external TPM, it becomes less clear.
> >
> 
> Those won't go away and will turn into case statements in C...
> 
>     stefan

Absolutely but case statements are easier to follow
than ifdef tricks.

-- 
MST

      reply	other threads:[~2015-06-02 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02  0:32 [Qemu-devel] [PATCH] tpm: Add missing common TPM SSDT file Stefan Berger
2015-06-02  6:48 ` Michael S. Tsirkin
2015-06-02 13:14   ` Stefan Berger
2015-06-02 13:22     ` Michael S. Tsirkin
2015-06-02 13:23       ` Stefan Berger
2015-06-02 13:31         ` Michael S. Tsirkin [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=20150602153044-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=stefanb@us.ibm.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).