From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"Michael Walle" <michael@walle.cc>,
"Gaël PORTAY" <gael.portay+rtone@gmail.com>,
"Chris Packham" <judge.packham@gmail.com>,
"Edgar Bonet" <bonet@grenoble.cnrs.fr>
Subject: Re: [Buildroot] [PATCH v6 3/5] linux: introduce BR2_LINUX_KERNEL_CUSTOM_DTS_DIR
Date: Tue, 4 Mar 2025 08:39:37 +0000 [thread overview]
Message-ID: <Z8a8SGiT2TiRaGYV@ryzen> (raw)
In-Reply-To: <Z7wyy7HiZ2KHCiVw@ryzen>
On Mon, Feb 24, 2025 at 09:50:19AM +0100, Niklas Cassel wrote:
> On Fri, Feb 21, 2025 at 11:55:27PM +0100, Romain Naour via buildroot wrote:
> >
> > Note: We want to create a list of dts files (LINUX_DTS_LIST) present in
> > diectrories listed by BR2_LINUX_KERNEL_CUSTOM_DTS_DIR. But
> > LINUX_DTS_LIST must not contain BR2_LINUX_KERNEL_CUSTOM_DTS_DIR
> > paths. Use GNU 'find' print format %P to print each dts file path
> > without their respective dts overlay directory path.
> > Do the same for LINUX_DTSO_LIST.
>
> Personally, I would drop this Note: from the commit message.
>
> I think that your commit message is doing a really good job of explaining
> the problem (and the solution), but I don't think it needs implementation
> details like this in the commit message.
>
> If you think this is important enough to keep, then it should probably be
> included as a comment next to the definition of LINUX_DTS_LIST instead of
> being in the commit message.
>
> Regardless (if you chose to kill it, or to have it as a comment), I don't
> think you need to send a new version just for this, it could be fixed up
> while applying.
>
> Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
This series seems to have stalled.
Did you decide to wait for 2025.02 to get released before applying?
Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-03-04 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 22:55 [Buildroot] [PATCH v6 1/5] linux: add support for device tree overlays Romain Naour via buildroot
2025-02-21 22:55 ` [Buildroot] [PATCH v6 2/5] configs/rock5b: build and install rock5b " Romain Naour via buildroot
2025-02-21 22:55 ` [Buildroot] [PATCH v6 3/5] linux: introduce BR2_LINUX_KERNEL_CUSTOM_DTS_DIR Romain Naour via buildroot
2025-02-24 8:50 ` Niklas Cassel via buildroot
2025-03-04 8:39 ` Niklas Cassel via buildroot [this message]
2025-02-21 22:55 ` [Buildroot] [PATCH v6 4/5] configs/acmesystems_acqua_a5_*: switch to BR2_LINUX_KERNEL_CUSTOM_DTS_DIR Romain Naour via buildroot
2025-02-21 22:55 ` [Buildroot] [PATCH v6 5/5] configs/acmesystems_acqua_a5_*: bump to Linux 6.12.9 Romain Naour via buildroot
2025-03-05 20:02 ` [Buildroot] [PATCH v6 1/5] linux: add support for device tree overlays Julien Olivain
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=Z8a8SGiT2TiRaGYV@ryzen \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=bonet@grenoble.cnrs.fr \
--cc=gael.portay+rtone@gmail.com \
--cc=judge.packham@gmail.com \
--cc=michael@walle.cc \
--cc=romain.naour@smile.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.