($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, ross.burton@arm.com
Cc: nd@arm.com
Subject: Re: [PATCH 01/10] arm/apply_local_src_patches: allow use in multiple directories
Date: Sun,  1 Oct 2023 16:15:22 -0400	[thread overview]
Message-ID: <169619132219.3169419.14023585507851002171.b4-ty@arm.com> (raw)
In-Reply-To: <20230929152128.3401009-1-ross.burton@arm.com>


On Fri, 29 Sep 2023 16:21:19 +0100, ross.burton@arm.com wrote:
> Pull out the patch application logic so the postfunc by default scans
> for patches in LOCAL_SRC_PATCHES_INPUT_DIR and applies them to
> LOCAL_SRC_PATCHES_DEST_DIR as before.
> 
> This allows recipes to inherit the class and directly call
> apply_local_src_patches as needed to process patches in multiple
> directories.
> 
> [...]

Applied, thanks!

[01/10] arm/apply_local_src_patches: allow use in multiple directories
        commit: be76055bdccaa476f6b68abf1ff26c007d4717c9
[02/10] arm/trusted-services: pass through CMake generator
        commit: 893b20fbee25b7a9a6791ec415fe6117ddeb2cd8
[03/10] arm/trusted-services: add missing pkgconfig inherit
        commit: 7a126f00ded5a4cf013df80e75198c1f55883eca
[04/10] arm/trusted-services/ts-remote-test: move binary to $bindir
        commit: 909d49fa6f5eaf3ee686b5f6c0eee5ed4a830d47
[05/10] arm/trusted-services/ts-sp-env-test: add missing DEPENDS
        commit: 549e05e486cb55697adf2fd068e6cc22dd194942
[06/10] arm/trusted-services/ts-sp-env-test: remove
        commit: 67deb2cf1bbfd343cc2bb847bd625a5e3b79ed74
[07/10] arm/trusted-services: use apply_local_src_patches
        commit: 46e6f42e31a239aee59255022742819ea1ed6aaf
[08/10] arm/trusted-services: upgrade nanopb and fix build races
        commit: 210a6ace832534cb1a492649e3e61532e9ca6a8f
[09/10] CI: use a venv for sphinx
        commit: dbad5d928199e3feae0acb43cc23c6daeacc7f1b
[10/10] CI: upgrade to Kas 4 container
        commit: 4d76ed4c75dbfef8bb444777dab9fae88e3dcaaa

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


      parent reply	other threads:[~2023-10-01 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 15:21 [PATCH 01/10] arm/apply_local_src_patches: allow use in multiple directories ross.burton
2023-09-29 15:21 ` [PATCH 02/10] arm/trusted-services: pass through CMake generator ross.burton
2023-09-29 15:21 ` [PATCH 03/10] arm/trusted-services: add missing pkgconfig inherit ross.burton
2023-09-29 15:21 ` [PATCH 04/10] arm/trusted-services/ts-remote-test: move binary to $bindir ross.burton
2023-09-29 15:21 ` [PATCH 05/10] arm/trusted-services/ts-sp-env-test: add missing DEPENDS ross.burton
2023-09-29 15:21 ` [PATCH 06/10] arm/trusted-services/ts-sp-env-test: remove ross.burton
2023-09-29 15:21 ` [PATCH 07/10] arm/trusted-services: use apply_local_src_patches ross.burton
2023-09-29 15:21 ` [PATCH 08/10] arm/trusted-services: upgrade nanopb and fix build races ross.burton
2023-09-29 15:21 ` [PATCH 09/10] CI: use a venv for sphinx ross.burton
2023-09-29 15:21 ` [PATCH 10/10] CI: upgrade to Kas 4 container ross.burton
2023-10-01 20:15 ` 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=169619132219.3169419.14023585507851002171.b4-ty@arm.com \
    --to=jdmason@kudzu.us \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=nd@arm.com \
    --cc=ross.burton@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).