From: Greg KH <greg@kroah.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Kylene Hall <kjhall@us.ibm.com>,
Nishanth Aravamudan <nacc@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char/tpm: use msleep(), clean-up timers, fix typo
Date: Fri, 15 Apr 2005 14:04:02 -0700 [thread overview]
Message-ID: <20050415210402.GA22834@kroah.com> (raw)
In-Reply-To: <29495f1d0504151344a33ee24@mail.gmail.com>
On Fri, Apr 15, 2005 at 01:44:55PM -0700, Nish Aravamudan wrote:
> On 4/15/05, Kylene Hall <kjhall@us.ibm.com> wrote:
> > I have tested this patch and agree that using msleep is the right. Please
> > apply this patch to the tpm driver. One hunk might fail b/c the
> > typo has been fixed already.
>
> Would you like me to respin the patch, Greg? Or is the failed hunk ok?
I'm sorry, but I am not in charge of accepting patches for the tpm
driver. Why not go through the listed maintainer for this process, they
should know how to get it into the mainline kernel tree properly. If
not, why would they be listed as the maintainer? :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-15 21:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 0:41 [BK PATCH] Add TPM driver support for 2.6.11 Greg KH
2005-03-10 0:42 ` [PATCH] Add TPM hardware enablement driver Greg KH
2005-03-10 0:42 ` [PATCH] tpm: fix cause of SMP stack traces Greg KH
2005-03-10 0:42 ` [PATCH] tpm_msc-build-fix Greg KH
2005-03-10 0:42 ` [PATCH] tpm_atmel build fix Greg KH
2005-03-10 0:42 ` [PATCH] tpm-build-fix Greg KH
2005-03-10 3:51 ` [PATCH] Add TPM hardware enablement driver Jeff Garzik
2005-03-15 23:59 ` Kylene Jo Hall
2005-03-17 0:32 ` Kylene Hall
2005-03-23 2:02 ` Jeff Garzik
2005-03-24 6:39 ` Greg KH
2005-03-24 21:04 ` Jeff Garzik
2005-03-24 21:33 ` Greg KH
2005-04-05 16:14 ` Kylene Jo Hall
2005-04-08 20:07 ` Kylene Jo Hall
2005-04-09 8:31 ` Ian Campbell
2005-04-27 22:15 ` [PATCH: 1 of 12] Fix concerns with TPM driver -- use enums Kylene Hall
2005-04-27 22:23 ` Greg KH
2005-04-27 22:15 ` [PATCH: 2 of 12 ] Fix TPM driver -- address missing const defs Kylene Hall
2005-04-27 22:16 ` [PATCH: 3 of 12] Fix TPM driver --remove unnecessary module stuff Kylene Hall
2005-04-27 22:16 ` [PATCH 4 of 12] Fix TPM driver -- read return code issue Kylene Hall
2005-04-27 22:16 ` [PATCH 5 of 12] Fix TPM driver -- large stack objects Kylene Hall
2005-04-27 22:18 ` [PATCH 6 of 12] Fix TPM driver -- how timer is initialized Kylene Hall
2005-04-27 22:18 ` [PATCH 7 of 12] Fix TPM driver -- use to_pci_dev Kylene Hall
2005-03-10 17:35 ` [PATCH] Add TPM hardware enablement driver Nish Aravamudan
2005-03-10 18:19 ` Nish Aravamudan
2005-03-10 19:09 ` [PATCH] char/tpm: use msleep(), clean-up timers, fix typo Nishanth Aravamudan
2005-03-10 21:04 ` [PATCH] Add TPM hardware enablement driver Alexey Dobriyan
2005-04-27 22:18 ` [PATCH 9 of 12] Fix TPM driver -- remove unnecessary __force Kylene Hall
2005-03-11 18:18 ` [PATCH] char/tpm: use msleep(), clean-up timers, fix typo Nishanth Aravamudan
2005-04-15 20:23 ` Kylene Hall
2005-04-15 20:44 ` Nish Aravamudan
2005-04-15 21:04 ` Greg KH [this message]
2005-04-15 21:47 ` Nish Aravamudan
2005-04-15 21:47 ` Nish Aravamudan
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=20050415210402.GA22834@kroah.com \
--to=greg@kroah.com \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=nish.aravamudan@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