All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: Emekcan Aras <Emekcan.Aras@arm.com>
Cc: Denys Dmytriyenko <denis@denix.org>,
	"meta-arm@lists.yoctoproject.org"
	<meta-arm@lists.yoctoproject.org>, Jon Mason <Jon.Mason@arm.com>
Subject: Re: [meta-arm] [PATCH 2/5] arm/optee: support optee 3.19
Date: Fri, 13 Jan 2023 10:38:41 +0000	[thread overview]
Message-ID: <A1B4DABC-7677-45B7-A68F-544D59EBF556@arm.com> (raw)
In-Reply-To: <Y8Ep5xNEyubVMHRj@e126835.cambridge.arm.com>

On 13 Jan 2023, at 09:52, Emekcan Aras <Emekcan.Aras@arm.com> wrote:
>>> +FILESEXTRAPATHS:prepend := "${THISDIR}/optee-os-3_19:"
>> 
>> Now, this is critical - why is there "3_19" version in the directory name?
>> 
> Out-of-tree patches that applies to 3.18 and 3.19 is very similar (naming-wise)
> but patches applies to different lines. In order to keep 3.18 patches, we needed
> to add 3.19 as a seperate directory.

It can’t use the automatic searching for PV as there *are* bbappends which bump the SHA to a post-release intermediate SHA and correctly set PV=3.19+git{SRCPV}, which is why there’s a 3.19 directory being added to the path.

I’d like it to be 3.19 and not 3_19 though.

Ross

  reply	other threads:[~2023-01-13 10:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 14:39 [PATCH 0/5] Add optee-os 3.19 recipe emekcan.aras
2022-12-21 14:39 ` [PATCH 1/5] arm/optee: Move optee-3.18 patches emekcan.aras
2022-12-21 14:39 ` [PATCH 2/5] arm/optee: support optee 3.19 emekcan.aras
2023-01-05 15:30   ` Ross Burton
2023-01-10 16:37     ` Jon Mason
2023-01-11  9:22       ` Emekcan Aras
2023-01-12 17:58   ` [meta-arm] " Denys Dmytriyenko
2023-01-12 18:15     ` Ross Burton
2023-01-13  9:52     ` Emekcan Aras
2023-01-13 10:38       ` Ross Burton [this message]
2022-12-21 14:39 ` [PATCH 3/5] arm-bsp/optee-os: Adds 3.19 bbappend emekcan.aras
2022-12-21 14:39 ` [PATCH 4/5] arm-bsp/optee-os: N1SDP support for optee-os 3.19 emekcan.aras
2022-12-21 14:39 ` [PATCH 5/5] arm/qemuarm-secureboot: pin optee-os version emekcan.aras
2022-12-21 15:37   ` [meta-arm] " Sumit Garg
2022-12-21 15:59     ` Emekcan Aras
2022-12-22  6:48       ` Sumit Garg
2022-12-22  8:42         ` Emekcan Aras
2022-12-23  5:47           ` Sumit Garg
2023-01-05 15:31             ` Ross Burton
2023-01-09 16:23 ` [PATCH 0/5] Add optee-os 3.19 recipe Jon Mason
2023-01-10 18:27 ` Jon Mason
2023-01-13 18:05 ` Jon Mason

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=A1B4DABC-7677-45B7-A68F-544D59EBF556@arm.com \
    --to=ross.burton@arm.com \
    --cc=Emekcan.Aras@arm.com \
    --cc=Jon.Mason@arm.com \
    --cc=denis@denix.org \
    --cc=meta-arm@lists.yoctoproject.org \
    /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.