From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/freeipmi: fix gcc 14.x issues
Date: Tue, 27 Aug 2024 18:24:12 +0200 [thread overview]
Message-ID: <20240827182412.5dbe3d78@windsurf> (raw)
In-Reply-To: <Zs1WjXQh8Hog59fF@waldemar-brodkorb.de>
On Tue, 27 Aug 2024 06:31:09 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Directly from upstream stable git repository, fixes for gcc 14.x
> issues. Only the changelog entries, which do not apply, where removed.
>
> Fixes:
>
> http://autobuild.buildroot.org/results/b33/b33e72b3348427f2f772e5c29dd3753958597058
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1->v2:
> - added Upstream tags to patch 0002/0003
> ---
> ...ipmi-sel-string-supermicro-common.h-.patch | 36 ++++++++++++
> ...sensors-fix-header-guard-definitions.patch | 57 +++++++++++++++++++
> ...003-ipmi-sensors-add-missing-include.patch | 28 +++++++++
> 3 files changed, 121 insertions(+)
> create mode 100644 package/freeipmi/0001-libfreeipmi-sel-ipmi-sel-string-supermicro-common.h-.patch
> create mode 100644 package/freeipmi/0002-ipmi-sensors-fix-header-guard-definitions.patch
> create mode 100644 package/freeipmi/0003-ipmi-sensors-add-missing-include.patch
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
prev parent reply other threads:[~2024-08-27 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 4:31 [Buildroot] [PATCH v2] package/freeipmi: fix gcc 14.x issues Waldemar Brodkorb
2024-08-27 16:24 ` 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=20240827182412.5dbe3d78@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 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.