public inbox for sophgo@lists.linux.dev
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Inochi Amaoto <inochiama@gmail.com>, Joshua Milas <josh.milas@gmail.com>
Cc: michael.opdenacker@rootcommit.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	unicorn_wang@outlook.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	alexander.sverdlin@gmail.com, rabenda.cn@gmail.com,
	thomas.bonnefille@bootlin.com, chao.wei@sophgo.com,
	liujingqi@lanxincomputing.com, devicetree@vger.kernel.org,
	sophgo@lists.linux.dev, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 2/3] arm64: dts: sophgo: add initial Milk-V Duo S board support
Date: Thu, 30 Oct 2025 12:50:01 +0000 (UTC)	[thread overview]
Message-ID: <b81536ee-5acf-4308-aa22-c374c4a3b8f7@rootcommit.com> (raw)
In-Reply-To: <7e37k5hdn7nnn7cxnfrzqfy7h7a3ofnaf4r6rgk7exehrhsn2i@rvxjxvh2sodw>

Hi Inochi,

Thanks a lot for the guidance!

On 10/29/25 01:53, Inochi Amaoto wrote:
> In fact, I see the maintainers do not agree adding every possible
> configuration to the DTS, (especially without "omit-if-unused" flag).
> And in many case, it is impossible to add all possibility. As a
> result, I prefer to use DTS overlay if there is something custom,
> and keep the mainline DTS minimum.

I guess you meant "/omit-if-no-ref/". Good to know!

> In fact the priority is the thing that is hard to decide. This is why
> I suggesting keeping compatible with the vendor kernel, as many people
> starts with vendor kernel and it is a good thing to refer.
This makes sense. Thanks again.
Cheers
Michael.

-- 
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/


  reply	other threads:[~2025-10-30 12:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11  1:48 [PATCH 0/3] Add initial Milk-V Duo S board support Joshua Milas
2025-10-11  1:48 ` [PATCH 1/3] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2025-10-11  1:50   ` Inochi Amaoto
2026-03-21 22:06     ` Joshua Milas
2025-10-11  1:48 ` [PATCH 2/3] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2025-10-11  1:56   ` Inochi Amaoto
2025-10-11 19:19     ` Joshua Milas
2025-10-13  0:43       ` Inochi Amaoto
2025-10-26 21:35         ` Joshua Milas
2025-10-26 22:48           ` Michael Opdenacker
2025-10-28 23:23             ` Joshua Milas
2025-10-29  0:53             ` Inochi Amaoto
2025-10-30 12:50               ` Michael Opdenacker [this message]
2025-10-11  1:48 ` [PATCH 3/3] riscv64: " Joshua Milas
2025-10-11  1:57   ` Inochi Amaoto
2025-10-11  2:16 ` [PATCH 0/3] Add " Chen Wang
2025-10-14  3:27 ` Chen Wang

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=b81536ee-5acf-4308-aa22-c374c4a3b8f7@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=alex@ghiti.fr \
    --cc=alexander.sverdlin@gmail.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=chao.wei@sophgo.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=inochiama@gmail.com \
    --cc=josh.milas@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=liujingqi@lanxincomputing.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rabenda.cn@gmail.com \
    --cc=robh@kernel.org \
    --cc=sophgo@lists.linux.dev \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=unicorn_wang@outlook.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