From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] board/friendlyarm: drop nanopi-neo
Date: Sat, 6 Aug 2022 23:24:43 +0200 [thread overview]
Message-ID: <20220806232443.1a74cb77@windsurf> (raw)
In-Reply-To: <20220806210800.176207-1-yann.morin.1998@free.fr>
On Sat, 6 Aug 2022 23:08:00 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> nanopi-neo no longer builds, as uboot needs python2 on the host:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/2812053540
>
> I no longer have access to that board, so I can't test an update to
> either uboot or the kernel anymore.
>
> Drop the board.
>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> board/friendlyarm/nanopi-neo/boot.cmd | 8 -----
> board/friendlyarm/nanopi-neo/genimage.cfg | 34 ------------------
> board/friendlyarm/nanopi-neo/readme.txt | 42 ----------------------
> configs/friendlyarm_nanopi_neo_defconfig | 43 -----------------------
> 4 files changed, 127 deletions(-)
> delete mode 100644 board/friendlyarm/nanopi-neo/boot.cmd
> delete mode 100644 board/friendlyarm/nanopi-neo/genimage.cfg
> delete mode 100644 board/friendlyarm/nanopi-neo/readme.txt
> delete mode 100644 configs/friendlyarm_nanopi_neo_defconfig
Applied to master after changing the commit title to use
"configs/friendlyarm_nanopi_neo: remove defconfig", and removing
entries in the DEVELOPERS file. 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:[~2022-08-06 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 21:08 [Buildroot] [PATCH] board/friendlyarm: drop nanopi-neo Yann E. MORIN
2022-08-06 21: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=20220806232443.1a74cb77@windsurf \
--to=buildroot@buildroot.org \
--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.