From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] oprofile: bump version to 0.9.4 and make architecture independent
Date: Fri, 25 Jul 2008 16:17:36 +0200 [thread overview]
Message-ID: <1216995456.18524.3.camel@localhost> (raw)
This patch will bump the version to 0.9.4 and let the build process be
architecture independent.
The old patches are not needed anymore, but a new patch for AVR32 has
been added to enable lookup_dcookie functionality.
Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oprofile-bump-and-fix.patch
Type: text/x-patch
Size: 12772 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080725/8b0bf0eb/attachment-0001.bin
next reply other threads:[~2008-07-25 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 14:17 Hans-Christian Egtvedt [this message]
2008-08-12 11:19 ` [Buildroot] [patch] oprofile: bump version to 0.9.4 and make architecture independent Hans-Christian Egtvedt
2008-09-11 15:08 ` Fathi Boudra
2008-09-12 15:50 ` Fathi Boudra
2008-09-15 12:52 ` Hans-Christian Egtvedt
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=1216995456.18524.3.camel@localhost \
--to=hans-christian.egtvedt@atmel.com \
--cc=buildroot@busybox.net \
/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