From: Denys Dmytriyenko <denis@denix.org>
To: Jon Mason <jdmason@kudzu.us>
Cc: Ryan Fairfax <rfairfax@microsoft.com>, meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH v2] arm/optee-os: Fix build race condition when building fTPM
Date: Tue, 11 Jan 2022 15:35:35 -0500 [thread overview]
Message-ID: <20220111203535.GD26229@denix.org> (raw)
In-Reply-To: <Yd3pTSN1vFxrcuOY@kudzu.us>
The patch is corrupted even visually - it lost all indentation and leading
whitespaces...
On Tue, Jan 11, 2022 at 03:32:13PM -0500, Jon Mason wrote:
> On Tue, Jan 11, 2022 at 11:38:26AM -0800, Ryan Fairfax wrote:
> > I posted from this list's web client to try to avoid encoding issues - in part because I cannot use easily alternative clients with my mail account. I'll see what I can do to get this resent but are there any specific errors that might help me understand what is getting modified?
>
> Using b4 is the easiest way to see
>
> $ b4 am -o - jKa2.1641920328439478855.fAON@lists.yoctoproject.org | git am -s
> Looking up https://lore.kernel.org/r/jKa2.1641920328439478855.fAON%40lists.yoctoproject.org
> Grabbing thread from lore.kernel.org/all
> Analyzing 1 messages in the thread
> ---
> Writing /tmp/tmpjx37s82ib4-am-stdout
> [PATCH v2] arm/optee-os: Fix build race condition when building fTPM
> ---
> Total patches: 1
> ---
> Link: https://lore.kernel.org/r/jKa2.1641920328439478855.fAON@lists.yoctoproject.org
> Base: not found (applies clean to current tree)
> ---
> Applying: arm/optee-os: Fix build race condition when building fTPM
> error: corrupt patch at line 11
> Patch failed at 0001 arm/optee-os: Fix build race condition when building fTPM
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
>
>
> One way around using an Outlook server is to use Gmail as the SMTP
> server and have it rewrite the address when it sends. See
> https://support.google.com/mail/answer/22370?hl=en
>
> I might have used this in the past :)
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2022-01-11 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yd3Wpf55ymc+BkZk@kudzu.us>
2022-01-11 19:38 ` [PATCH v2] arm/optee-os: Fix build race condition when building fTPM Ryan Fairfax
[not found] ` <Yd3pTSN1vFxrcuOY@kudzu.us>
2022-01-11 20:35 ` Denys Dmytriyenko [this message]
2022-01-11 20:57 ` Ryan Fairfax
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=20220111203535.GD26229@denix.org \
--to=denis@denix.org \
--cc=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
--cc=rfairfax@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.