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@xxxxxxxxx > > 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@xxxxxxxxxx> (✓ DKIM/kernel.org) > > ERROR: missing [2/2]! > > --- > > Total patches: 1 > > --- > > WARNING: Thread incomplete! > > Link:https://lore.kernel.org/r/20220116012627.2031-1-tstruk@xxxxxxxxx > > 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@xxxxxxxxx> > > and the second is: > > Message-Id: <20220116012627.2031-2-tstruk@xxxxxxxxx> > > and contains: > > In-Reply-To: <20220116012627.2031-1-tstruk@xxxxxxxxx> > References: <20220116012627.2031-1-tstruk@xxxxxxxxx> > > 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
