From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: "Alejandro González" <alejandro.gonzalez.correo@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 1/2] package/watchdogd: bump to version 3.5
Date: Sat, 4 Dec 2021 21:49:25 +0100 [thread overview]
Message-ID: <20211204214925.4609145b@windsurf> (raw)
In-Reply-To: <0f7d1dfe-07c3-198f-3449-9179db0e385c@gmail.com>
On Sat, 4 Dec 2021 21:23:23 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:
> Very unfortunate name clash between include files in two packages.
Yes, I had followed this.
> http://autobuild.buildroot.net/results/185c753af2aa159b494b13f78b0826dddbe4aed6
>
> However, I think it's highly unlikely they'll be enabled at the same
> time. My recommendation is to go for next and let 2021.11 out the door.
But if the build issue exists in master, we need to fix it in master,
or the issue will keep popping up again and again in the autobuilders.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-04 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 1:39 [Buildroot] [PATCH next 0/2] fix name clash between libite and LiTE Joachim Wiberg
2021-12-02 1:39 ` [Buildroot] [PATCH next 1/2] package/watchdogd: bump to version 3.5 Joachim Wiberg
2021-12-04 20:04 ` Thomas Petazzoni
2021-12-04 20:23 ` Joachim Wiberg
2021-12-04 20:49 ` Thomas Petazzoni [this message]
2021-12-04 20:59 ` Yann E. MORIN
2021-12-05 7:53 ` Joachim Wiberg
2021-12-02 1:39 ` [Buildroot] [PATCH next 2/2] package/libite: bump to version 2.5.1 Joachim Wiberg
2021-12-05 19:14 ` [Buildroot] [PATCH next 0/2] fix name clash between libite and LiTE Yann E. MORIN
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=20211204214925.4609145b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=alejandro.gonzalez.correo@gmail.com \
--cc=buildroot@buildroot.org \
--cc=troglobit@gmail.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