Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <gary.bisson@boundarydevices.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: chris.dimich@boundarydevices.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/nitrogen8mp: update device trees list
Date: Mon, 22 Nov 2021 08:51:33 +0100	[thread overview]
Message-ID: <YZtMBbJdQR2k33Qr@p1g2> (raw)
In-Reply-To: <20211121215846.64208e7d@windsurf>

Hi Thomas,

On Sun, Nov 21, 2021 at 09:58:46PM +0100, Thomas Petazzoni wrote:
> Hello Gary,
> 
> On Fri, 19 Nov 2021 15:36:32 +0100
> Gary Bisson <gary.bisson@boundarydevices.com> wrote:
> 
> > - remove the A0 device tree as this (pre-prod) version of the CPU isn't
> > supported any longer
> > - add '-m4' variant to enable remoteproc api to Cortex-M core
> > - add ENC variants for our ENC carrier [1] (+ 1 with tc358743 support)
> > 
> > [1]
> > https://boundarydevices.com/product/nitrogen8m-plus-enc-carrier-board/
> > 
> > Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
> 
> Applied to master, thanks!
> 
> > This fixes the build of the kernel for this board as the a0 dtb doesn't
> > exist any more. But I couldn't find any report of the defconfig failing,
> > are those still built regularly?
> 
> It definitely failed recently, see
> https://gitlab.com/buildroot.org/buildroot/-/jobs/1795045913

I saw this right after sending my email ;) Thanks for merging this fix
quickly!

Thanks,
Gary
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-11-22  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 14:36 [Buildroot] [PATCH] configs/nitrogen8mp: update device trees list Gary Bisson
2021-11-21 20:58 ` Thomas Petazzoni
2021-11-22  7:51   ` Gary Bisson [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=YZtMBbJdQR2k33Qr@p1g2 \
    --to=gary.bisson@boundarydevices.com \
    --cc=buildroot@buildroot.org \
    --cc=chris.dimich@boundarydevices.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