From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Conor Dooley <conor@kernel.org>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: Emil Renner Berthing <kernel@esmil.dk>,
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>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Jacob Keller <jacob.e.keller@intel.com>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v6 0/4] Enable networking support for StarFive JH7100 SoC
Date: Wed, 31 Jan 2024 13:29:47 +0200 [thread overview]
Message-ID: <f9fe53a4-c3b0-4e61-b607-40959c2d6c4c@collabora.com> (raw)
In-Reply-To: <ae15ab84-fb1b-4da6-803d-6fd5ad46ce24@collabora.com>
Hi Conor,
On 1/10/24 18:17, Cristian Ciocaltea wrote:
> On 1/10/24 15:57, Conor Dooley wrote:
>> On Tue, Dec 26, 2023 at 02:38:26PM -0600, Emil Renner Berthing wrote:
>>> Cristian Ciocaltea wrote:
>>>> This patch series adds ethernet support for the StarFive JH7100 SoC and
>>>> makes it available for the StarFive VisionFive V1 and BeagleV Starlight
>>>> boards, although I could only validate on the former SBC. Thank you Emil
>>>> and Geert for helping with tests on BeagleV!
>>>>
>>>> The work is heavily based on the reference implementation [1] and depends
>>>> on the SiFive Composable Cache controller and non-coherent DMA support
>>>> provided by Emil via [2] and [3].
>>>>
>>>> *Update 1*: As of next-20231214, dependencies [2] & [3] have been merged.
>>>>
>>>> *Update 2*: Since v5, the dwmac patches will be handled via [4], while the
>>>> clock patches subset via [5].
>>>
>>> I'm not sure my rb my sense when I'm listed as a co-developer, but this version
>>> looks good to me:
>>>
>>> Reviewed-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
>>
>> Cool, thanks. Cristian, can you ping this series once the binding gets
>> picked up by the netdev folks after the merge window closes?
>
> Sure, will do!
The binding has been applied on net-next [1].
Thanks,
Cristian
[1]: https://lore.kernel.org/lkml/170669882745.1676.8675995195978883744.git-patchwork-notify@kernel.org/
next prev parent reply other threads:[~2024-01-31 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 21:17 [PATCH v6 0/4] Enable networking support for StarFive JH7100 SoC Cristian Ciocaltea
2023-12-20 21:17 ` [PATCH v6 1/4] riscv: dts: starfive: jh7100: Add sysmain and gmac DT nodes Cristian Ciocaltea
2023-12-20 21:17 ` [PATCH v6 2/4] riscv: dts: starfive: jh7100-common: Setup pinmux and enable gmac Cristian Ciocaltea
2023-12-20 21:17 ` [PATCH v6 3/4] riscv: dts: starfive: visionfive-v1: Setup ethernet phy Cristian Ciocaltea
2023-12-20 21:17 ` [PATCH v6 4/4] riscv: dts: starfive: beaglev-starlight: Setup phy reset gpio Cristian Ciocaltea
2023-12-26 20:38 ` [PATCH v6 0/4] Enable networking support for StarFive JH7100 SoC Emil Renner Berthing
2024-01-10 13:57 ` Conor Dooley
2024-01-10 16:17 ` Cristian Ciocaltea
2024-01-31 11:29 ` Cristian Ciocaltea [this message]
2024-01-31 12:25 ` Conor Dooley
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=f9fe53a4-c3b0-4e61-b607-40959c2d6c4c@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=andrew@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=jacob.e.keller@intel.com \
--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=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richardcochran@gmail.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