From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Michael Riesch <michael.riesch@wolfvision.net>,
Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] DNM: dts: arm64: rockchip: copy pf5 device tree from mainline Linux
Date: Fri, 12 Apr 2024 15:33:00 +0200 [thread overview]
Message-ID: <3c5fd58a-6d49-4eca-ae39-d507acc35f8c@pengutronix.de> (raw)
In-Reply-To: <12f46e93-c50f-4c3b-9052-eb25c5448d88@wolfvision.net>
Hi,
On 12.04.24 15:02, Michael Riesch wrote:
> Hi Marco,
>
> Thanks for your response!
>
> On 4/5/24 19:02, Marco Felsch wrote:
>> Hi Michael,
>>
>> thanks for your patches.
>>
>>> DNM: dts: arm64: rockchip: copy pf5 device tree from
>>
>> I suppose DNM means "do not merge", instead of marking it this way we
>> put the not yet upstream Linux dts files into arch as well but mark them
>> as upstream dts file, e.g.:
>>
>> - arch/arm/dts/imx8mm-innocomm-wb15-evk-upstream.dts
>> - arch/arm/dts/imx8mp-debix-model-a-upstream.dts
>> - arch/arm/dts/imx8mp-debix-som-a-bmb-08-upstream.dts
>> - arch/arm/dts/imx8mp-debix-som-a-upstream.dtsi
I have been wondering if we should add yet another device tree
directory for kernel DTs that are not yet in the kernel, e.g.
common/boards/dts. Then we can place full DTs there, remove them
once they are in dts/ and clean up arch/$ARCH/dts/ that way.
> OK, I'll do it that way!
>
>> Once the files are usptream we can remove them.
>
> Is this something I should keep in mind or may I expect that this
> happens automagically?
Usually, when someone notices. Having them in a single directory
as suggested above may make it easier to sport no longer needed DTs.
Thoughts?
Cheers,
Ahmad
>
>> On 24-04-05, Michael Riesch wrote:
>>> [...]
> Best regards,
> Michael
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-04-12 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 14:04 [PATCH 0/4] arm: boards: add wolfvision pf5 mainboard Michael Riesch
2024-04-05 14:04 ` [PATCH 1/4] DNM: dts: arm64: rockchip: copy pf5 device tree from mainline Linux Michael Riesch
2024-04-05 17:02 ` Marco Felsch
2024-04-12 13:02 ` Michael Riesch
2024-04-12 13:33 ` Ahmad Fatoum [this message]
2024-04-12 15:46 ` Marco Felsch
2024-04-16 13:39 ` Sascha Hauer
2024-04-05 14:04 ` [PATCH 2/4] common: add wolfvision board code library Michael Riesch
2024-04-08 6:27 ` Sascha Hauer
2024-04-05 14:04 ` [PATCH 3/4] arm: dts: add common state for wolfvision boards Michael Riesch
2024-04-05 14:04 ` [PATCH 4/4] arm: boards: add wolfvision pf5 mainboard Michael Riesch
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=3c5fd58a-6d49-4eca-ae39-d507acc35f8c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
--cc=michael.riesch@wolfvision.net \
/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