All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, Jose Quaresma <quaresma.jose@gmail.com>
Cc: ricardo@foundries.io, Jose Quaresma <jose.quaresma@foundries.io>
Subject: Re: [PATCH 1/3] optee-ftpm/optee-os: add missing space in EXTRA_OEMAKE
Date: Thu, 27 Oct 2022 17:38:38 -0400	[thread overview]
Message-ID: <166690671826.1783399.14113675841760772359.b4-ty@arm.com> (raw)
In-Reply-To: <20221026141854.1557213-1-jose.quaresma@foundries.io>

On Wed, 26 Oct 2022 14:18:52 +0000, Jose Quaresma wrote:
> When append to variable a space is required at the beginning.

Applied, thanks!

[1/3] optee-ftpm/optee-os: add missing space in EXTRA_OEMAKE
      commit: 518294d518968a9f8895a17c5d6d0f1a95246ef3
[2/3] optee-ftpm/optee-os: rewite in a way to be less error prone
      (no commit info)
[3/3] optee-os-ts: avoid using escape chars in EXTRA_OEMAKE
      commit: 3080a94bde5a2f316960bc6a6c649f798a76e239

Best regards,
-- 
Jon Mason <jon.mason@arm.com>


      parent reply	other threads:[~2022-10-27 21:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 14:18 [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space in EXTRA_OEMAKE Jose Quaresma
2022-10-26 14:18 ` [meta-arm][PATCH 2/3] optee-ftpm/optee-os: rewite in a way to be less error prone Jose Quaresma
2022-10-27  6:19   ` Mikko Rapeli
2022-10-27  9:01     ` Jose Quaresma
2022-10-27 14:03   ` Jon Mason
2022-10-27 14:26     ` Jose Quaresma
2022-10-26 14:18 ` [meta-arm][PATCH 3/3] optee-os-ts: avoid using escape chars in EXTRA_OEMAKE Jose Quaresma
2022-10-27  6:20   ` Mikko Rapeli
2022-10-27 14:06     ` Jon Mason
2022-10-27  6:18 ` [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space " Mikko Rapeli
2022-10-27  8:57   ` Jose Quaresma
2022-10-27 21:38 ` Jon Mason [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=166690671826.1783399.14113675841760772359.b4-ty@arm.com \
    --to=jdmason@kudzu.us \
    --cc=jose.quaresma@foundries.io \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=quaresma.jose@gmail.com \
    --cc=ricardo@foundries.io \
    /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.