public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Michael Zhu <michael.zhu@starfivetech.com>,
	Drew Fustini <drew@beagleboard.org>,
	Emil Renner Berthing <kernel@esmil.dk>,
	<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <kernel@collabora.com>
Subject: Re: [PATCH v3 0/3] Enable initial support for StarFive VisionFive V1 SBC
Date: Tue, 4 Oct 2022 10:52:24 +0100	[thread overview]
Message-ID: <YzwCWDN4NyIQ8a46@wendy> (raw)
In-Reply-To: <c5169131-486e-9808-ba48-b7abe1be6a99@collabora.com>

On Mon, Oct 03, 2022 at 02:06:32PM +0300, Cristian Ciocaltea wrote:
> Please let me know if there is anything else missing in order to get this
> queued for merging.

Hey Cristian,

LinusW has applied a conflicting change for 6.1 as he renamed the
pinctrl header that you have moved from one file to another in this
patch [0]. Could you rebase once that lands upstream please?

Thanks,
Conor.

0 - https://lore.kernel.org/linux-riscv/CACRpkdZmmMjVwpHxkJP+Ui0XJgrdZx8kpVybifbwkRB1_uMhAg@mail.gmail.com/

> 
> Thanks,
> Cristian
> 
> On 9/8/22 17:29, Cristian Ciocaltea wrote:
> > The StarFive VisionFive V1 SBC [1] is similar with the already supported
> > BeagleV Starlight Beta board, both being based on the StarFive JH7100 SoC.
> > 
> > In addition to documenting the necessary compatibles, this patch series
> > moves most of the content from jh7100-beaglev-starlight.dts to a new file
> > jh7100-common.dtsi, to be shared between the two boards.
> > 
> > No other changes are required in order to successfully boot the board.
> > 
> > [1] https://github.com/starfive-tech/VisionFive
> > 
> > Changes in v3:
> >   - Added Reviewed-by tag from Krzysztof in patch 1/3
> >   - Optimized patch 2/3 by enabling copy detection on "git format-patch",
> >     as indicated by Krzysztof
> > 
> > Changes in v2:
> >   - Simplified documentation by using 'enum' instead of 'const' in
> >     patch 1/3, according to Conor's review
> >   - Added Reviewed-by tags from Conor
> > 
> > Cristian Ciocaltea (3):
> >    dt-bindings: riscv: starfive: Add StarFive VisionFive V1 board
> >    riscv: dts: starfive: Add common DT for JH7100 based boards
> >    riscv: dts: starfive: Add StarFive VisionFive V1 device tree
> > 
> >   .../devicetree/bindings/riscv/starfive.yaml   |   4 +-
> >   arch/riscv/boot/dts/starfive/Makefile         |   2 +-
> >   .../dts/starfive/jh7100-beaglev-starlight.dts | 153 +-----------------
> >   ...aglev-starlight.dts => jh7100-common.dtsi} |   3 -
> >   .../jh7100-starfive-visionfive-v1.dts         |  20 +++
> >   5 files changed, 25 insertions(+), 157 deletions(-)
> >   copy arch/riscv/boot/dts/starfive/{jh7100-beaglev-starlight.dts => jh7100-common.dtsi} (96%)
> >   create mode 100644 arch/riscv/boot/dts/starfive/jh7100-starfive-visionfive-v1.dts
> > 
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
> 

  reply	other threads:[~2022-10-04  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 14:29 [PATCH v3 0/3] Enable initial support for StarFive VisionFive V1 SBC Cristian Ciocaltea
2022-09-08 14:29 ` [PATCH v3 1/3] dt-bindings: riscv: starfive: Add StarFive VisionFive V1 board Cristian Ciocaltea
2022-09-08 14:29 ` [PATCH v3 2/3] riscv: dts: starfive: Add common DT for JH7100 based boards Cristian Ciocaltea
2022-09-08 14:29 ` [PATCH v3 3/3] riscv: dts: starfive: Add StarFive VisionFive V1 device tree Cristian Ciocaltea
2022-10-03 11:06 ` [PATCH v3 0/3] Enable initial support for StarFive VisionFive V1 SBC Cristian Ciocaltea
2022-10-04  9:52   ` Conor Dooley [this message]
2022-10-04 10:15     ` Cristian Ciocaltea
2022-10-17 21:14       ` Cristian Ciocaltea

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=YzwCWDN4NyIQ8a46@wendy \
    --to=conor.dooley@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drew@beagleboard.org \
    --cc=kernel@collabora.com \
    --cc=kernel@esmil.dk \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.zhu@starfivetech.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    /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