From: Jarkko Sakkinen <jarkko@kernel.org>
To: Tadeusz Struk <tstruk@gmail.com>
Cc: Shuah Khan <shuah@kernel.org>,
linux-integrity@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] selftests: tpm: add async space test with noneexisting handle
Date: Mon, 17 Jan 2022 03:44:59 +0200 [thread overview]
Message-ID: <YeTKG3qPxm2DJGCN@iki.fi> (raw)
In-Reply-To: <070044a5-5468-1095-334f-67cf98eb30b3@gmail.com>
On Sun, Jan 16, 2022 at 02:43:32PM -0800, Tadeusz Struk wrote:
> On 1/16/22 12:04, Jarkko Sakkinen wrote:
> > $ b4 am20220116012627.2031-2-tstruk@gmail.com
> > Looking uphttps://lore.kernel.org/r/20220116012627.2031-2-tstruk%40gmail.com
> > Grabbing thread from lore.kernel.org/all/20220116012627.2031-2-tstruk%40gmail.com/t.mbox.gz
> > Analyzing 4 messages in the thread
> > Will use the latest revision: v4
> > You can pick other revisions using the -vN flag
> > Checking attestation on all messages, may take a moment...
> > ---
> > ✓ [PATCH v4 1/2] tpm: Fix error handling in async work
> > ✓ Signed: DKIM/gmail.com
> > + Reviewed-by: Jarkko Sakkinen<jarkko@kernel.org> (✓ DKIM/kernel.org)
> > ERROR: missing [2/2]!
> > ---
> > Total patches: 1
> > ---
> > WARNING: Thread incomplete!
> > Link:https://lore.kernel.org/r/20220116012627.2031-1-tstruk@gmail.com
> > Base: applies clean to current tree
> > git am ./v4_20220115_tstruk_tpm_fix_error_handling_in_async_work.mbx
> >
> > The patch set is broken. It has patches from two different patch sets.
> >
> > I saved the 2nd patch from my email client.
>
> I'm not sure why it doesn't like it. They both are generated with the same
> git format-patch command. If you look at the source, the first one is:
>
> Message-Id: <20220116012627.2031-1-tstruk@gmail.com>
>
> and the second is:
>
> Message-Id: <20220116012627.2031-2-tstruk@gmail.com>
>
> and contains:
>
> In-Reply-To: <20220116012627.2031-1-tstruk@gmail.com>
> References: <20220116012627.2031-1-tstruk@gmail.com>
>
> Maybe it doesn't like the fact that the first in v4 and the second in v3?
> Do you need me to do anything else to get that applied?
>
> --
> Thanks,
> Tadeusz
NP, Both are applied now.
BR, Jarkko
next prev parent reply other threads:[~2022-01-17 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 1:26 [PATCH v4 1/2] tpm: Fix error handling in async work Tadeusz Struk
2022-01-16 1:26 ` [PATCH v3 2/2] selftests: tpm: add async space test with noneexisting handle Tadeusz Struk
2022-01-16 14:34 ` Jarkko Sakkinen
2022-01-16 20:04 ` Jarkko Sakkinen
2022-01-16 22:43 ` Tadeusz Struk
2022-01-17 1:44 ` Jarkko Sakkinen [this message]
2022-01-17 2:55 ` Tadeusz Struk
2022-01-17 7:02 ` Jarkko Sakkinen
2022-01-16 14:34 ` [PATCH v4 1/2] tpm: Fix error handling in async work Jarkko Sakkinen
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=YeTKG3qPxm2DJGCN@iki.fi \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tstruk@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
all inboxes | Powered by JetHome®