Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Leo Liang <ycliang@andestech.com>
Cc: <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] configs/andes_ae350_45: remove defconfig, broken
Date: Tue, 19 Aug 2025 11:54:59 +0200	[thread overview]
Message-ID: <20250819115459.34b62b9b@windsurf> (raw)
In-Reply-To: <aKRGPS7VOFk7VNCs@swlinux02>

Hello Leo,

On Tue, 19 Aug 2025 17:39:09 +0800
Leo Liang <ycliang@andestech.com> wrote:

> My apologies for not catching the CI failure earlier;
> my email filter was misconfigured.

OK.

> I've fixed the Linux tarball link and confirmed that the defconfig builds.

When you say you "fixed the Linux tarball", you mean you re-added the
missing branch to your Github repo?

Note that the defconfig is apparently using a branch, which is not
correct. It should either use a tag or a commit hash. Indeed, branches
can change over time, while our defconfigs should be reproducible.

> Would it be possible to drop this patch?

I'll drop the patch, but aside from the branch vs. tag issue above,
there are other issues to fix in your defconfig:

Patches lack an "Upstream" tag:

board/andes/ae350/patches/uboot/0001-mmc-ftsdc010_mci-Support-DTS-of-ftsdc010-driver-for-.patch lib_patch.Upstream
board/andes/ae350/patches/uboot/0002-spl-Align-device-tree-blob-address-at-8-byte-boundar.patch lib_patch.Upstream

The post-build shell script doesn't pass Shellcheck:

board/andes/ae350/post-build.sh Shellcheck

Hashes are missing for the defconfig:

configs/andes_ae350_45_defconfig lib_defconfig.ForceCheckHash

Could you please address all those issues to keep the defconfig in a
properly maintained state?

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

  reply	other threads:[~2025-08-19  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 20:32 [Buildroot] [PATCH] configs/andes_ae350_45: remove defconfig, broken Thomas Petazzoni via buildroot
2025-08-19  9:39 ` Leo Liang via buildroot
2025-08-19  9:54   ` Thomas Petazzoni via buildroot [this message]
2025-08-19 10:17     ` Leo Liang via buildroot
2025-08-19 17:08       ` Thomas Petazzoni via buildroot

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=20250819115459.34b62b9b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=ycliang@andestech.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