mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kylene Jo Hall <kjhall@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	TPM Device Driver List <tpmdd-devel@lists.sourceforge.net>
Subject: Re: [PATCH] tpm: fix missing string
Date: Thu, 20 Apr 2006 09:07:22 -0500	[thread overview]
Message-ID: <1145542042.4894.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20060420005938.6c3d4319.akpm@osdl.org>

On Thu, 2006-04-20 at 00:59 -0700, Andrew Morton wrote:
> Kylene Jo Hall <kjhall@us.ibm.com> wrote:
> >
> > A string corresponding to the tcpa_pc_event_id POST_CONTENTS was missing
> >  causing an overflow bug when access was attempted in the get_event_name
> >  function.
> 
> These last two bugs are applicable to 2.6.17.
Correct.
> 
> I'm kind of thinking of pushing all the TPM patches into 2.6.17 actually. 
> Although there's quite a lot of feature work in there, we also have
> bugfixes, although relatively minor ones.
> 
> What's your confidence level in those patches?

> Would you have time to do a decent round of regression testing against the
> resulting TPM code prior to 2.6.17?  Say, inside the next couple of weeks?

I'm pretty confident.  Yesterday's bug fixes were the last things I know
of that needed attention.  I'd be happy to run regression testing in the
next couple of weeks.

Thanks,
Kylie


      reply	other threads:[~2006-04-20 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 19:13 Kylene Jo Hall
2006-04-20  7:59 ` Andrew Morton
2006-04-20 14:07   ` Kylene Jo Hall [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=1145542042.4894.33.camel@localhost.localdomain \
    --to=kjhall@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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
all inboxes | Powered by JetHome®