public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH] RECIPE-API-CHANGELOG.md: update the correct kernel header package name.
Date: Fri, 22 Aug 2025 14:19:01 +0530	[thread overview]
Message-ID: <20250822084901.3601592-1-srinuvasan.a@siemens.com> (raw)

From: Srinuvasan A <srinuvasan.a@siemens.com>

Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
 RECIPE-API-CHANGELOG.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index 8468717d..d8e0c01f 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -326,7 +326,7 @@ Output file names now include distro name and architecture/machine name parts.
 ### Using custom package name for linux kernel and headers
 
 Isar assumes that linux kernel is provided by linux-image-${KERNEL_NAME}
-package, while headers are provided by linux-image-${KERNEL_NAME} package.
+package, while headers are provided by linux-headers-${KERNEL_NAME} package.
 This naming may be different in other distributions like Raspberry Pi OS.
 
 KERNEL_IMAGE_PKG and KERNEL_HEADERS_PKG variables allow to use custom package
-- 
2.34.1

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20250822084901.3601592-1-srinuvasan.a%40siemens.com.

             reply	other threads:[~2025-08-22  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22  8:49 srinuvasan.a via isar-users [this message]
2025-08-22 14:19 ` 'MOESSBAUER, Felix' via isar-users

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=20250822084901.3601592-1-srinuvasan.a@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=srinuvasan.a@siemens.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