Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yang Shi <yang.shi@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: dvhart@linux.intel.com
Subject: [PATCH] Revert "hello-mod: Ensure the produced package name begins with kernel-module-"
Date: Wed, 14 Aug 2013 09:41:54 -0700	[thread overview]
Message-ID: <1376498514-23057-2-git-send-email-yang.shi@windriver.com> (raw)
In-Reply-To: <1376498514-23057-1-git-send-email-yang.shi@windriver.com>

[YOCTO #4286]

The package runtime mapping rename issue is already fixed by
commit 0bc564af07c1bae8112f834a60aea3b72af7de13, the "kernel-module-" workaround
is not necessary anymore for out-of-tree module package, so revert that commit.

This reverts commit 71aafc214fe407b7620e747c11dfb8326c867b1c.

Signed-off-by: Yang Shi <yang.shi@windriver.com>
---
 .../recipes-kernel/hello-mod/hello-mod_0.1.bb      |    8 --------
 1 files changed, 0 insertions(+), 8 deletions(-)

diff --git a/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb b/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
index 621f700..64a6dda 100644
--- a/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
+++ b/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
@@ -13,11 +13,3 @@ SRC_URI = "file://Makefile \
           "
 
 S = "${WORKDIR}"
-
-# Kernel module packages MUST begin with 'kernel-module-', otherwise
-# multilib image generation can fail.
-#
-# The following line is only necessary if the recipe name does not begin
-# with kernel-module-.
-#
-PKG_${PN} = "kernel-module-${PN}"
-- 
1.7.5.4



  reply	other threads:[~2013-08-14 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 16:41 Revert kernel-moudle- workaround for out-of-tree module package Yang Shi
2013-08-14 16:41 ` Yang Shi [this message]
2013-08-14 18:10   ` [PATCH] Revert "hello-mod: Ensure the produced package name begins with kernel-module-" Darren Hart
2013-08-14 18:35     ` Mark Hatle
2013-08-16 15:23       ` Yang Shi

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=1376498514-23057-2-git-send-email-yang.shi@windriver.com \
    --to=yang.shi@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox