Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/valgrind: bump to version 3.15.0
Date: Wed, 24 Apr 2019 21:25:04 +0200	[thread overview]
Message-ID: <20190424212504.42aa3ce6@windsurf> (raw)
In-Reply-To: <1556110027-11297-1-git-send-email-stefan.maksimovic@rt-rk.com>

Hello,

On Wed, 24 Apr 2019 14:47:07 +0200
Stefan Maksimovic <stefan.maksimovic@rt-rk.com> wrote:

> Additionally, provide a patch with which valgrind
> can be now compiled for MIPS32r6/MIPS64r6 and
> reenable it in the config file.
> 
> Moreover, remove a patch which is not needed anymore
> since https://bugs.kde.org/show_bug.cgi?id=400975
> has been resolved.
> 
> Signed-off-by: Stefan Maksimovic <stefan.maksimovic@rt-rk.com>
> ---
>  ...e.ac-disable-gcc-march-mips64r2-detection.patch | 49 ----------------------
>  ...x-mips32r6-and-mips64r6-compilation-issue.patch | 46 ++++++++++++++++++++
>  package/valgrind/Config.in                         |  7 +---
>  package/valgrind/valgrind.hash                     |  2 +-
>  package/valgrind/valgrind.mk                       |  5 +--
>  5 files changed, 49 insertions(+), 60 deletions(-)
>  delete mode 100644 package/valgrind/0003-configure.ac-disable-gcc-march-mips64r2-detection.patch
>  create mode 100644 package/valgrind/0003-mips-fix-mips32r6-and-mips64r6-compilation-issue.patch

Applied to master, thanks. It would have been better to clearly
indicate that the patch you are adding is backported from upstream.
I've amended the commit log, and the patch description itself, with
this information.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-04-24 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 12:47 [Buildroot] [PATCH] package/valgrind: bump to version 3.15.0 Stefan Maksimovic
2019-04-24 19:25 ` Thomas Petazzoni [this message]

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=20190424212504.42aa3ce6@windsurf \
    --to=thomas.petazzoni@bootlin.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