Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/atop: update to 2.11.0
Date: Wed, 14 Aug 2024 23:48:06 +0200	[thread overview]
Message-ID: <20240814234806.59de8028@windsurf> (raw)
In-Reply-To: <Zrrin+t5g/czHuKA@waldemar-brodkorb.de>

On Tue, 13 Aug 2024 06:35:43 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> See here for a changelog:
> https://atoptool.nl/downloadatop.php
> 
> Fixes:
>  - http://autobuild.buildroot.net/results/4f2/4f256c96c8b7c34c1f1be378ad3a535d3150e44d
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1->v2:
>  - use $(TARGET_MAKE_ENV) to let atop find pkg-config, suggested by
>    Thomas P.
> ---
>  ...he-user-to-pass-additional-CFLAGS-an.patch | 21 +++++++++----------
>  package/atop/atop.hash                        |  2 +-
>  package/atop/atop.mk                          |  4 ++--
>  3 files changed, 13 insertions(+), 14 deletions(-)

I usually don't like applying bumps to master at this point, but atop
was added in this release cycle, so it cannot get more "broken", and
therefore: 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:[~2024-08-14 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  4:35 [Buildroot] [PATCH v2] package/atop: update to 2.11.0 Waldemar Brodkorb
2024-08-14 21:48 ` 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=20240814234806.59de8028@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.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