All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Conor.Dooley@microchip.com
Cc: wg@grandegger.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	Daire.McNamara@microchip.com, linux-can@vger.kernel.org,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH net-next 0/2] Document PolarFire SoC can controller
Date: Mon, 13 Jun 2022 15:45:12 +0200	[thread overview]
Message-ID: <20220613134512.t74de4dytxbdbg7k@pengutronix.de> (raw)
In-Reply-To: <4c5b43bd-a255-cbc1-c7a3-9a79e34d2e91@microchip.com>


[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]

On 13.06.2022 12:52:00, Conor.Dooley@microchip.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.

regards,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

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

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Conor.Dooley@microchip.com
Cc: wg@grandegger.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	Daire.McNamara@microchip.com, linux-can@vger.kernel.org,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH net-next 0/2] Document PolarFire SoC can controller
Date: Mon, 13 Jun 2022 15:45:12 +0200	[thread overview]
Message-ID: <20220613134512.t74de4dytxbdbg7k@pengutronix.de> (raw)
In-Reply-To: <4c5b43bd-a255-cbc1-c7a3-9a79e34d2e91@microchip.com>

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

On 13.06.2022 12:52:00, Conor.Dooley@microchip.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.

regards,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2022-06-13 13:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  6:54 [PATCH net-next 0/2] Document PolarFire SoC can controller Conor Dooley
2022-06-07  6:54 ` Conor Dooley
2022-06-07  6:54 ` [PATCH net-next 1/2] dt-bindings: can: mpfs: document the mpfs " Conor Dooley
2022-06-07  6:54   ` Conor Dooley
2022-06-07 16:19   ` Rob Herring
2022-06-07 16:19     ` Rob Herring
2022-06-07  6:55 ` [PATCH net-next 2/2] riscv: dts: microchip: add mpfs's can controllers Conor Dooley
2022-06-07  6:55   ` Conor Dooley
2022-06-07  7:15 ` [PATCH net-next 0/2] Document PolarFire SoC can controller Marc Kleine-Budde
2022-06-07  7:15   ` Marc Kleine-Budde
2022-06-07  7:52   ` Conor.Dooley
2022-06-07  7:52     ` Conor.Dooley
2022-06-07  8:28     ` Marc Kleine-Budde
2022-06-07  8:28       ` Marc Kleine-Budde
2022-06-07  8:54       ` Conor.Dooley
2022-06-07  8:54         ` Conor.Dooley
2022-06-13 12:52         ` Conor.Dooley
2022-06-13 12:52           ` Conor.Dooley
2022-06-13 13:45           ` Marc Kleine-Budde [this message]
2022-06-13 13:45             ` Marc Kleine-Budde
2022-06-13 13:48             ` Conor.Dooley
2022-06-13 13:48               ` 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=20220613134512.t74de4dytxbdbg7k@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Conor.Dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=wg@grandegger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.