Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/3] strace: add patch allowing compilation with kernel	headers >= 2.6.32
Date: Wed, 12 Jan 2011 17:30:38 -0700	[thread overview]
Message-ID: <4D2E47AE.5060803@mentor.com> (raw)
In-Reply-To: <1294867230-7827-1-git-send-email-eric@eukrea.com>

On 01/12/2011 02:20 PM, Eric Bénard wrote:
> tested with kernel headers 2.6.31&  2.6.37 : both compile fine.

Is there a reason to not switch to 4.5.20, or even newer instead?

>
> Signed-off-by: Eric Bénard<eric@eukrea.com>
> ---
>   recipes/strace/strace_4.5.14.bb |    3 ++-
>   1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/strace/strace_4.5.14.bb b/recipes/strace/strace_4.5.14.bb
> index 33a44ad..395e4ee 100644
> --- a/recipes/strace/strace_4.5.14.bb
> +++ b/recipes/strace/strace_4.5.14.bb
> @@ -1,7 +1,7 @@
>   DESCRIPTION = "strace is a system call tracing tool."
>   SECTION = "console/utils"
>   LICENSE = "BSD"
> -PR = "r9"
> +PR = "r10"
>
>   SRC_URI = "${SOURCEFORGE_MIRROR}/strace/strace-${PV}.tar.bz2 \
>              file://glibc-2.5.patch \
> @@ -13,6 +13,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/strace/strace-${PV}.tar.bz2 \
>              file://strace-arm-no-cachectl.patch \
>              file://strace-dont-include-linux-dirent-h.patch \
>              file://mips-sigcontext.patch \
> +           file://strace-linux-2.6.32.patch \
>             "
>
>   # The strace-4.5.14-avr32.patch conflicts with some other patches.


-- 
Tom Rini
Mentor Graphics Corporation



  parent reply	other threads:[~2011-01-13  0:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 21:20 [PATCH 1/3] strace: add patch allowing compilation with kernel headers >= 2.6.32 Eric Bénard
2011-01-12 21:20 ` [PATCH 2/3] busybox 1.18.1: add latest fix Eric Bénard
2011-01-12 21:20   ` [PATCH 3/3] mtd-utils: add 1.4.1 Eric Bénard
2011-01-13  0:31     ` Tom Rini
2011-01-13 13:07       ` Eric Bénard
2011-01-13 13:54         ` Enrico Scholz
2011-01-13 14:31           ` Eric Bénard
2011-01-13 14:33             ` [PATCH v2] " Eric Bénard
2011-01-13 15:15               ` Tom Rini
2011-01-14  3:26               ` Khem Raj
2011-01-14 10:23                 ` Martin Jansa
2011-01-13  5:52     ` [PATCH 3/3] " Khem Raj
2011-01-13  5:50   ` [PATCH 2/3] busybox 1.18.1: add latest fix Khem Raj
2011-01-13  0:30 ` Tom Rini [this message]
2011-01-13  7:39   ` [PATCH 1/3] strace: add patch allowing compilation with kernel headers >= 2.6.32 Eric Bénard
2011-01-13 15:13     ` Tom Rini
2011-01-13 15:17       ` Eric Bénard
2011-01-13  5:49 ` Khem Raj
2011-01-13  7:39   ` Eric Bénard
2011-01-13 13:45   ` [PATCH v2] " Eric Bénard
2011-01-13 15:15     ` Tom Rini
2011-01-13 15:29       ` Eric Bénard
2011-01-13 20:34       ` [PATCH] strace 4.5.20: stable since 04/14/2010 so remove DP=-1 Eric Bénard
2011-01-13 21:06         ` Tom Rini
2011-01-13 21:15           ` [PATCH v2] " Eric Bénard
2011-01-13 21:29             ` Tom Rini
2011-01-14  3:30             ` Khem Raj
2011-01-14  3:28       ` [PATCH v2] strace: add patch allowing compilation with kernel headers >= 2.6.32 Khem Raj
2011-01-14  3:15     ` Khem Raj

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=4D2E47AE.5060803@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@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