All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: yann.morin.1998@free.fr, mmayer@broadcom.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/cpulimit: Backport a fix for an infrequent crash
Date: Thu, 2 Jun 2022 16:04:18 +0200	[thread overview]
Message-ID: <20220602160418.519f17f9@windsurf> (raw)
In-Reply-To: <20220519220747.455528-1-f.fainelli@gmail.com>

On Thu, 19 May 2022 15:07:46 -0700
Florian Fainelli <f.fainelli@gmail.com> wrote:

> Backport the fix submitted from this pull request:
> 
> https://github.com/opsengine/cpulimit/pull/61
> 
> to fix an infrequent crash.
> 
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  .../0003-Fix-an-infrequent-crash.patch        | 26 +++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 package/cpulimit/0003-Fix-an-infrequent-crash.patch

Both applied to master. PATCH 2/2 isn't really a fix, but it makes
sense to have it in master IMO instead of this weird special case for
the or1k/musl situation.

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

      parent reply	other threads:[~2022-06-02 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 22:07 [Buildroot] [PATCH 1/2] package/cpulimit: Backport a fix for an infrequent crash Florian Fainelli
2022-05-19 22:07 ` [Buildroot] [PATCH 2/2] package/cpulimit: Remove or1k/musl limitation Florian Fainelli
2022-06-02 14:04 ` 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=20220602160418.519f17f9@windsurf \
    --to=buildroot@buildroot.org \
    --cc=f.fainelli@gmail.com \
    --cc=mmayer@broadcom.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.