From: Peter Korsgaard <peter@korsgaard.com>
To: "Sassen, Rutger" <rsassen@comecer.com>
Cc: Peter Seiderer <ps.report@gmx.net>,
Martin Bark <martin@barkynet.com>,
Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v3 1/1] package/rpi-firmware: fix missing files in overlays
Date: Wed, 23 Mar 2022 22:40:09 +0100 [thread overview]
Message-ID: <87ee2se4au.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <YQXPR01MB61216162093E0D5F17304D0BAE129@YQXPR01MB6121.CANPRD01.PROD.OUTLOOK.COM> (Rutger Sassen's message of "Thu, 17 Mar 2022 11:06:22 +0000")
>>>>> "Sassen," == Sassen, Rutger <rsassen@comecer.com> writes:
> When supporting multiple hardware targets, overlay_map.dtb might
> be needed to map overlay names to one of several implementations.
> Signed-off-by: Rutger Sassen <rsassen@comecer.com>
> ---
> Changes v2 -> v3:
> - in Config.in use if statement instead of depends (suggested by Peter
> Seiderer)
> - mention the filename overlay_map.dtb in the help text (suggested by
> Peter Seiderer)
> Changes v1 -> v2:
> - instead of always copying overlay_map.dtb, make it configurable
> (suggested by Peter Seiderer)
> - do not copy README since it a special case, only needed when
> installing overlays to a non-standard location (suggested by Peter
> Seiderer)
Committed to 2021.02.x, 2021.11.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-03-23 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 11:06 [Buildroot] [PATCH v3 1/1] package/rpi-firmware: fix missing files in overlays Sassen, Rutger
2022-03-17 18:03 ` Peter Seiderer
2022-03-17 19:02 ` Bartosz Bilas
2022-03-21 21:56 ` Arnout Vandecappelle
2022-03-22 8:16 ` [Buildroot] [External] " Sassen, Rutger
2022-03-23 19:35 ` [Buildroot] " Peter Seiderer
2022-03-23 19:49 ` Peter Seiderer
2022-03-23 20:06 ` Arnout Vandecappelle
2022-03-23 21:40 ` Peter Korsgaard [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=87ee2se4au.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=mahyar.koshkouei@gmail.com \
--cc=martin@barkynet.com \
--cc=ps.report@gmx.net \
--cc=rsassen@comecer.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 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.