Re: [can-next-rfc 1/7] can: m_can: update link to M_CAN user manual

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 14.12.20 10:37, Marc Kleine-Budde wrote:
On 12/14/20 10:31 AM, Oliver Hartkopp wrote:


On 12.12.20 18:55, Marc Kleine-Budde wrote:
Old versions of the user manual are regularly depublished, so change link to
point to the product page instead. This will be hopefully more stable.

Signed-off-by: Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx>
---
   drivers/net/can/m_can/m_can.c | 3 +--
   1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
index 06c136961c7c..8873f6f6f6da 100644
--- a/drivers/net/can/m_can/m_can.c
+++ b/drivers/net/can/m_can/m_can.c
@@ -5,8 +5,7 @@
   // Copyright (C) 2018-19 Texas Instruments Incorporated - http://www.ti.com/
/* Bosch M_CAN user manual can be obtained from:
- * http://www.bosch-semiconductors.de/media/pdf_1/ipmodules_1/m_can/
- * mcan_users_manual_v302.pdf
+ * https://www.bosch-semiconductors.com/ip-modules/can-ip-modules/m-can/
    */

This URL update makes it just 'a little' better.

Would it make sense to move

https://github.com/hartkopp/M_CAN-User-Manual-History

to

https://github.com/linux-can/M_CAN-User-Manual-Archive

and rework the README.md in a way that it's just an archive of already
published content?

make it so!

While watching the button to create a new repo I thought about a more generic name.

What about
https://github.com/linux-can/can-doc-archive
https://github.com/linux-can/can-doc
https://github.com/linux-can/can-drv-doc
... ?

where we can create a m_can directory (as named in the kernel).

Regards,
Oliver



[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux