From: tom.zanussi@linux.intel.com
To: openembedded-core@lists.openembedded.org,
bruce.ashfield@windriver.com, dvhart@linux.intel.com
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/2] perf recipe update
Date: Thu, 7 Mar 2013 18:38:57 -0600 [thread overview]
Message-ID: <cover.1362702690.git.tom.zanussi@linux.intel.com> (raw)
From: Tom Zanussi <tom.zanussi@linux.intel.com>
With the 3.8 kernel update, we need a new perf recipe to match. Well,
not really, because there's nothing 3.4-specific about the current one,
and there's nothing tying it to a specific version of the kernel.
This acknowledges that by getting rid fo the version number. It also
adds a minor cleanup to rename the current include file to something
more appropriate.
The following changes since commit d823759b4594143d522eae0b2a2498436a6dcb1e:
core-image.bbclass: support read-only rootfs (2013-03-07 11:20:02 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git tzanussi/rename-perf-v0
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/rename-perf-v0
Tom Zanussi (2):
perf: rename perf.inc to perf-features.inc
perf: rename perf_3.4 to perf
meta/recipes-kernel/perf/{perf.inc => perf-features.inc} | 0
meta/recipes-kernel/perf/{perf_3.4.bb => perf.bb} | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/perf/{perf.inc => perf-features.inc} (100%)
rename meta/recipes-kernel/perf/{perf_3.4.bb => perf.bb} (99%)
--
1.7.11.4
next reply other threads:[~2013-03-08 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 0:38 tom.zanussi [this message]
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
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=cover.1362702690.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=bruce.ashfield@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 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.