public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: 曹珊珊 <sandie.cao@deepcomputing.io>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Emil Renner Berthing <kernel@esmil.dk>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Heiko Stuebner <heiko.stuebner@cherry.de>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	rafal@milecki.pl, Linus Walleij <linus.walleij@linaro.org>,
	Michael Zhu <michael.zhu@starfivetech.com>,
	Drew Fustini <drew@beagleboard.org>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, dhs@frame.work, ams@frame.work,
	gregkh@linuxfoundation.org, yuning.liang@deepcomputing.io,
	huiming.qiu@deepcomputing.io
Subject: Re: [patch v2 2/3] dt-bindings: riscv: starfive: add deepcomputing,fm7110
Date: Tue, 24 Sep 2024 17:16:44 +0100	[thread overview]
Message-ID: <20240924-pacemaker-unstylish-3807c3c4f106@spud> (raw)
In-Reply-To: <407ce3d77416bb2522b7906b0df3d5adf02c27ee.1182851f.8778.42ba.bd71.b04cef6fccc0@feishu.cn>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Tue, Sep 24, 2024 at 06:12:02PM +0800, 曹珊珊 wrote:
> On 24/09/2024 10:06, Sandie Cao wrote:
> > Add deepcomputing,fm7110 into compatible list.
> 
> A: 
> DeepComputing is creating a RISC-V Framework Laptop 13 Mainboard 
> powered by a StarFive JH7110 processor.This is a developer-focused 
> product, aimed at making tinkering with RISC-V more accessible.
> The Mainboard is under development and we'll share more on functionality, 
> compatibility, and availability as the program progresses.
> For this Mainboard, the Model name in Framework is Framework FRANME0000;
> the Model name in DeepComputing is DeepComputing fm7110.
> 
> Q: This we see from the diff. And commit subject. Describe here the hardware.

Please don't use this quoting style, please figure out how to do
proper inline quoting with your mail client.

> 
> > Signed-off-by: Sandie Cao <sandie.cao@deepcomputing.io>
> 
> Best regards,
> Krzysztof
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2024-09-24 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  8:06 [patch v2 2/3] dt-bindings: riscv: starfive: add deepcomputing,fm7110 Sandie Cao
2024-09-24  8:25 ` Krzysztof Kozlowski
     [not found]   ` <407ce3d77416bb2522b7906b0df3d5adf02c27ee.1182851f.8778.42ba.bd71.b04cef6fccc0@feishu.cn>
2024-09-24 16:16     ` Conor Dooley [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=20240924-pacemaker-unstylish-3807c3c4f106@spud \
    --to=conor@kernel.org \
    --cc=ams@frame.work \
    --cc=aou@eecs.berkeley.edu \
    --cc=devicetree@vger.kernel.org \
    --cc=dhs@frame.work \
    --cc=drew@beagleboard.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko.stuebner@cherry.de \
    --cc=huiming.qiu@deepcomputing.io \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.zhu@starfivetech.com \
    --cc=neil.armstrong@linaro.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rafal@milecki.pl \
    --cc=robh@kernel.org \
    --cc=sandie.cao@deepcomputing.io \
    --cc=yuning.liang@deepcomputing.io \
    /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