From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Milan Broz <gmazyland@gmail.com>,
linux-integrity@vger.kernel.org, James Morris <jmorris@namei.org>
Subject: Re: [PATCH] tpm: Fix null pointer dereference on chip register error path
Date: Mon, 08 Jul 2019 17:33:08 +0300 [thread overview]
Message-ID: <c72431a1e275d94203a62c99337cca40c20a43c9.camel@linux.intel.com> (raw)
In-Reply-To: <1324e0d6-74c4-f8a7-ea9f-0a603bf15e93@gmail.com>
On Fri, 2019-07-05 at 23:23 +0200, Milan Broz wrote:
> On 05/07/2019 19:52, Jarkko Sakkinen wrote:
> > So how should we work this one out? Do you want to create v2 or do I
> > create a new patch and put reported-by tag. Both work for me. I just
> > need to know this.
>
> Please fix you mail filters, the patch was sent more than day ago.
>
>
https://lore.kernel.org/linux-integrity/20190704072615.31143-1-gmazyland@gmail.com/T/#u
>
> Milan
Nothing wrong with my mail filters, it was actually waiting in my inbox.
Just didn't notice it that it was part of the emails I downloaded to my
laptop with fdm on Friday (because in rush to spend weekend). Didn't
have time to go through all of them during that day.
/Jarkko
prev parent reply other threads:[~2019-07-08 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 8:42 [PATCH] tpm: Fix null pointer dereference on chip register error path Milan Broz
2019-06-12 20:57 ` James Morris
2019-06-14 21:56 ` Sasha Levin
2019-06-15 6:28 ` Milan Broz
2019-06-28 7:56 ` Milan Broz
2019-07-02 18:37 ` Jarkko Sakkinen
2019-07-03 23:01 ` Jarkko Sakkinen
2019-07-04 7:26 ` [PATCH v2] " Milan Broz
2019-07-08 14:34 ` Jarkko Sakkinen
2019-07-08 14:44 ` Jarkko Sakkinen
2019-07-05 17:52 ` [PATCH] " Jarkko Sakkinen
2019-07-05 21:23 ` Milan Broz
2019-07-08 14:33 ` Jarkko Sakkinen [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=c72431a1e275d94203a62c99337cca40c20a43c9.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gmazyland@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
/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).