All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: Vincent Jardin <vjardin@free.fr>,
	Romain Naour <romain.naour@smile.fr>,
	arnout@rnout.be, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3] boot/uboot: support custom DTS with CONFIG_OF_UPSTREAM
Date: Mon, 19 Oct 2026 09:42:49 +0200	[thread overview]
Message-ID: <atXJ5ikWcKB2ouMm@windsurf> (raw)
In-Reply-To: <c5aca2bcccb4018ee1d1923ce3262177977003eb.camel@gmail.com>

On Sun, Oct 18, 2026 at 09:45:45PM +0200, Alexander Sverdlin wrote:

> > Could you clarify why we would want this change? I'm kind of missing
> > the point.
> 
> This is indeed a valid point!
> I've been looking into it from the point of implementing a BSP for a board
> which have been already merged into upstream Linux, but not into U-Boot
> yet, but you are right, for this intermediate step I'm not forced to
> use CONFIG_OF_UPSTREAM even if it would be used for the same board at
> some point in future (when the DTs will be merged into U-Boot as well).
> 
> Sorry for the noise, let's ignore the patch for now!

Thanks for your feedback! I'll mark the patch as Rejected then.

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:[~2026-10-19  7:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 21:06 [Buildroot] [PATCH v3] boot/uboot: support custom DTS with CONFIG_OF_UPSTREAM Alexander Sverdlin
2026-10-18 19:32 ` Thomas Petazzoni via buildroot
2026-10-18 19:45   ` Alexander Sverdlin
2026-10-19  7:42     ` 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=atXJ5ikWcKB2ouMm@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alexander.sverdlin@gmail.com \
    --cc=arnout@rnout.be \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vjardin@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.