From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ashley Lai <ashley@ashleylai.com>,
Rajiv Andrade <mail@srajiv.net>,
Marcel Selhorst <tpmdd@selhorst.net>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] tpm/tpm_i2c_stm_st33: Check return code of get_burstcount (fix CID: 986658)
Date: Wed, 30 Oct 2013 20:38:04 +0100 [thread overview]
Message-ID: <201310302038.04122.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20131030030747.GA12179@kroah.com>
Hi Greg,
> It [the CID] is noise as not everyone can see it or make anything out of it,
> so please don't include it.
I'll remove it from my tree before sending out the pull request to James.
Thanks for your opinion.
Peter
next prev parent reply other threads:[~2013-10-30 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 23:54 [PATCH] tpm/tpm_i2c_stm_st33: Check return code of get_burstcount (fix CID: 986658) Peter Huewe
2013-10-30 0:06 ` Greg KH
2013-10-30 0:42 ` Peter Hüwe
2013-10-30 3:07 ` Greg KH
2013-10-30 19:38 ` Peter Hüwe [this message]
2013-11-04 3:44 ` Ben Hutchings
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=201310302038.04122.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=ashley@ashleylai.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@srajiv.net \
--cc=stable@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.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