From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Louis Aussedat <aussedat.louis@gmail.com>,
Filip Skoneczny <fskoneczny@gmail.com>,
Marek Belisko <marek.belisko@open-nandra.com>,
Thomas Huth <huth@tuxfamily.org>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
Davide Viti <zinosat@gmail.com>,
Mike Harmony <mike.harmony@snapav.com>,
Peter Seiderer <ps.report@gmx.net>,
Jagan Teki <jagan@amarulasolutions.com>,
Suniel Mahesh <sunil@amarulasolutions.com>,
Romain Naour <romain.naour@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] Buildroot defconfigs about to be removed
Date: Mon, 8 Aug 2022 10:28:05 +0200 [thread overview]
Message-ID: <20220808102805.2ee4fa4c@windsurf> (raw)
In-Reply-To: <CAEyMn7ZtrsEdo18p2pjvdhrROnSemX2spZyxN8Tj67RLTcZG-w@mail.gmail.com>
Hello Heiko,
On Sun, 7 Aug 2022 00:28:46 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> This is the first time I have been informed about this build failure.
> I am surprised that I did not get any mail about this.
Sorry, your issue is potentially new. It's mainly the other issues that
I have already reported in the past, and which did not get any
feedback, on defconfigs that are not properly maintained (all those
friendlyarm/bananapi/orangepi boards).
> Nonetheless I will fix that and send a patch.
Thanks a lot!
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:[~2022-08-08 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 20:43 [Buildroot] Buildroot defconfigs about to be removed Thomas Petazzoni via buildroot
2022-08-06 22:28 ` Heiko Thiery
2022-08-08 8:28 ` Thomas Petazzoni via buildroot [this message]
2022-08-12 6:32 ` Suniel Mahesh
2022-08-08 8:14 ` Thomas Huth
2022-08-08 8:26 ` Thomas Petazzoni via buildroot
2022-08-08 19:59 ` Thomas Huth
2022-08-12 13:52 ` Thomas Petazzoni via buildroot
2022-08-15 9:50 ` Thomas Huth
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=20220808102805.2ee4fa4c@windsurf \
--to=buildroot@buildroot.org \
--cc=aussedat.louis@gmail.com \
--cc=fskoneczny@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=heiko.thiery@gmail.com \
--cc=huth@tuxfamily.org \
--cc=jagan@amarulasolutions.com \
--cc=marek.belisko@open-nandra.com \
--cc=mike.harmony@snapav.com \
--cc=ps.report@gmx.net \
--cc=romain.naour@gmail.com \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
--cc=zinosat@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