From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: tom.zanussi@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] perf: rename perf_3.4 to perf
Date: Tue, 12 Mar 2013 13:24:30 -0700 [thread overview]
Message-ID: <513F8EFE.2030604@linux.intel.com> (raw)
In-Reply-To: <513E6EC3.7090905@linux.intel.com>
On 03/11/2013 04:54 PM, Saul Wold wrote:
> On 03/07/2013 04:39 PM, tom.zanussi@linux.intel.com wrote:
>> From: Tom Zanussi <tom.zanussi@linux.intel.com>
>>
>> There's nothing kernel-version-specific about the perf_3.4 recipe, so
>> it's actually misnamed and misleading now that it also gets used with
>> the 3.8 kernel.
>>
>> Since the recipe isn't tied to a specific PV, and simply uses
>> whatever's in STAGING_KERNEL_DIR, there's no reason to add anything
>> else either to the bare PN, so just use that as the recipe name.
>>
> This did not quite work out correctly, since the package name has now
> gone backwards since the default PV for a recipe is 1.0 when nothing is
> set on the recipe file name.
>
> Is there a way to sort this out such that it picks up an incrementing PV
> from the kernel recipe?
>
> As it stands now, the PV has gone from 3.4 -> 1.0.
>
> Thanks for looking after this.
This is what PE is for right? Sounds like we need an epoch bump.
--
Darren hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-03-12 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 0:38 [PATCH 0/2] perf recipe update tom.zanussi
2013-03-08 0:39 ` [PATCH 1/2] perf: rename perf.inc to perf-features.inc tom.zanussi
2013-03-08 0:39 ` [PATCH 2/2] perf: rename perf_3.4 to perf tom.zanussi
2013-03-11 23:54 ` Saul Wold
2013-03-12 18:39 ` Richard Purdie
2013-03-12 20:24 ` Darren Hart [this message]
2013-03-08 1:06 ` [PATCH 0/2] perf recipe update Bruce Ashfield
2013-03-08 18:40 ` Darren Hart
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=513F8EFE.2030604@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
--cc=tom.zanussi@linux.intel.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.