Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Oleksandr G Zhadan <oleks@arcturusnetworks.com>
Cc: Michael Durrant <mdurrant@ArcturusNetworks.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/arcturus_ucp1020: remove defconfig, broken
Date: Tue, 19 Aug 2025 23:52:40 +0200	[thread overview]
Message-ID: <20250819235240.3642326c@windsurf> (raw)
In-Reply-To: <08a9d67a-1a2f-45f9-b494-2cde99cacd9b@arcturusnetworks.com>

Hello Oleksandr, Michael,

On Tue, 19 Aug 2025 17:02:19 -0400
Oleksandr G Zhadan <oleks@arcturusnetworks.com> wrote:

> The changes affected only our p1020 kernel branch.
> 
> There were no changes in buildroot.
> 
> Now `make arcturus_ucp1020_defconfig; make` generates images as expected.

Thanks for the feedback, I'll mark my patch as Rejected.

However, the kernel you're using is based on Linux 4.4, which is no
longer maintained, which isn't great, and which sooner or later will
mean that it won't build with newer compilers as Linux 4.4 no longer
receives any fixes/updates. Perhaps you need to get the support for
your platform in the upstream Linux kernel?

Best regards,

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 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 20:36 [Buildroot] [PATCH] configs/arcturus_ucp1020: remove defconfig, broken Thomas Petazzoni via buildroot
2025-08-19 20:37 ` Michael Durrant
2025-08-19 21:02   ` Oleksandr G Zhadan
2025-08-19 21:52     ` 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=20250819235240.3642326c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=mdurrant@ArcturusNetworks.com \
    --cc=oleks@arcturusnetworks.com \
    --cc=thomas.petazzoni@bootlin.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