All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: a-christidis@ti.com
Cc: meta-arago@lists.yoctoproject.org, reatmon@ti.com
Subject: Re: [meta-arago][master][PATCH v2 2/3] meta-arago-test: recipes-extended: Specify correct PV for OCL C headers
Date: Mon, 8 Sep 2025 11:21:08 -0400	[thread overview]
Message-ID: <20250908152108.GC3125@denix.org> (raw)
In-Reply-To: <20250905233849.2506703-3-a-christidis@ti.com>

Please don't use "meta-arago-test: recipes-extended:" prefix in the commit 
summary (Subject) - it's very high level and absolutely useless.

The convention that OE layers use is to specify the "area:", which is usually 
the name of the recipe for a single change, or a common name for multiple 
changes in the same commit, e.g. "conf/machine:" or even "opencl:" here.

So, this would change current subject

"meta-arago-test: recipes-extended: Specify correct PV for OCL C headers"

into

"opencl-headers: specify correct PV"

And for #3:

"opencl-clhpp: update v2.0.16 -> v2024.05.08"

In other words, instead of doing this:

"blah: blah: blah: do foo for bar"

do this:

"bar: do foo"


On Fri, Sep 05, 2025 at 06:38:48PM -0500, Antonios Christidis via lists.yoctoproject.org wrote:
> From: Antonios Christidis <a-christidis@ti.com>
> 
> With the .bbappend and .inc file, the version of the headers is
> increased. So, specify the correct PV of the headers.
> 
> Signed-off-by: Antonios Christidis <a-christidis@ti.com>
> ---
>  meta-arago-test/recipes-extended/opencl/opencl_headers-ti.inc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta-arago-test/recipes-extended/opencl/opencl_headers-ti.inc b/meta-arago-test/recipes-extended/opencl/opencl_headers-ti.inc
> index 48335204..1216adf5 100644
> --- a/meta-arago-test/recipes-extended/opencl/opencl_headers-ti.inc
> +++ b/meta-arago-test/recipes-extended/opencl/opencl_headers-ti.inc
> @@ -1,6 +1,7 @@
>  inherit cmake
>  
>  SRCREV = "8275634cf9ec31b6484c2e6be756237cb583999d"
> +PV = "2024.05.08"
>  
>  EXTRA_OECMAKE = "-DBUILD_TESTING=OFF"
>  
> -- 
> 2.34.1


  reply	other threads:[~2025-09-08 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 23:38 [meta-arago][master][PATCH v2 0/3] opencl-clhpp v2.0.16 -> v2024.05.08 a-christidis
2025-09-05 23:38 ` [meta-arago][master][PATCH v2 1/3] meta-arago-test: recipes-extended: Cmake support for opencl-headers a-christidis
2025-09-05 23:38 ` [meta-arago][master][PATCH v2 2/3] meta-arago-test: recipes-extended: Specify correct PV for OCL C headers a-christidis
2025-09-08 15:21   ` Denys Dmytriyenko [this message]
2025-09-08 16:02     ` Ryan Eatmon
2025-09-05 23:38 ` [meta-arago][master][PATCH v2 3/3] meta-arago-test: recipes-extended: opencl-clhpp v2.0.16 -> v2024.05.08 a-christidis
2025-09-05 23:40 ` [meta-arago][master][PATCH v2 0/3] " PRC Automation
2025-09-06  1:34 ` Andrew Davis
2025-09-08 13:47   ` Antonios Christidis

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=20250908152108.GC3125@denix.org \
    --to=denis@denix.org \
    --cc=a-christidis@ti.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.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.