Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Ziegler <br015@umbiko.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/boost: backport development branch changes to fix MIPS64 build failure
Date: Mon, 7 Nov 2022 23:05:52 +0100	[thread overview]
Message-ID: <20221107230552.04be0058@windsurf> (raw)
In-Reply-To: <20221107100527.2772772-1-br015@umbiko.net>

On Mon,  7 Nov 2022 11:05:27 +0100
Andreas Ziegler <br015@umbiko.net> wrote:

> Backport from Boost/intrusive development branch. Fixes issue introduced with 
> version 1.80.
> 
> Issue: https://github.com/boostorg/intrusive/issues/79
> Fixes: http://autobuild.buildroot.net/results/6cb/6cbc0672f3c5046405793d8cdc8f961d2ffb1d3e
> 
> Signed-off-by: Andreas Ziegler <br015@umbiko.net>
> ---
>  .../0001-Improve-modfunc-performance.patch    | 550 ++++++++++++++++++
>  1 file changed, 550 insertions(+)
>  create mode 100644 package/boost/0001-Improve-modfunc-performance.patch

I've added a link to the upstream commit within the patch itself, and
applied to master. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-11-07 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 10:05 [Buildroot] [PATCH] package/boost: backport development branch changes to fix MIPS64 build failure Andreas Ziegler
2022-11-07 22:05 ` Thomas Petazzoni via buildroot [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=20221107230552.04be0058@windsurf \
    --to=buildroot@buildroot.org \
    --cc=br015@umbiko.net \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox