[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0f837e2b-8333-07e5-9adb-e0f40ed17135@microchip.com>
Date: Mon, 13 Jun 2022 13:48:55 +0000
From: <Conor.Dooley@...rochip.com>
To: <mkl@...gutronix.de>, <Conor.Dooley@...rochip.com>
CC: <wg@...ndegger.com>, <davem@...emloft.net>, <edumazet@...gle.com>,
<kuba@...nel.org>, <pabeni@...hat.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <palmer@...belt.com>,
<paul.walmsley@...ive.com>, <aou@...s.berkeley.edu>,
<Daire.McNamara@...rochip.com>, <linux-can@...r.kernel.org>,
<netdev@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH net-next 0/2] Document PolarFire SoC can controller
On 13/06/2022 14:45, Marc Kleine-Budde wrote:
> On 13.06.2022 12:52:00, Conor.Dooley@...rochip.com wrote:
>>>> The register map cannot be downloaded directly anymore. For reference:
>>>>
>>>> http://web.archive.org/web/20220403030214/https://www.microsemi.com/document-portal/doc_download/1244581-polarfire-soc-register-map
>>>
>>> Oh that sucks. I know we have had some website issues over the weekend
>>> which might be the problem there. I'll try to bring it up and find out.
>>>
>>
>> Hey Marc,
>> Doc is still not available but should be getting fixed.
>
> Thanks.
>
>> What do I need to do for this binding? Are you happy to accept it without
>> a driver if I add links to the documentation and a working link to the
>> register map?
>
> I'm taking both patches and change the CAN into capital letters while
> applying, I'll also add a link to the datasheets.
Cool, SGTM.
Thanks,
Conor.
Powered by blists - more mailing lists