All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Nyekjaer <sean@geanix.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Cc: kernel@pengutronix.de, Dan Murphy <dmurphy@ti.com>,
	Sriram Dash <sriram.dash@samsung.com>
Subject: Re: [can-next-rfc 1/7] can: m_can: update link to M_CAN user manual
Date: Mon, 14 Dec 2020 09:11:32 +0100	[thread overview]
Message-ID: <c7850081-4a94-7feb-172d-c0cfe18304a8@geanix.com> (raw)
In-Reply-To: <20201212175518.139651-2-mkl@pengutronix.de>



On 12/12/2020 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@pengutronix.de>
Reviewed-by: Sean Nyekjaer <sean@geanix.com>
> ---
>   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/
>    */
>   
>   #include <linux/interrupt.h>
>
> base-commit: 46d5e62dd3c34770f3bfd0642daa9a7772a00362


  reply	other threads:[~2020-12-14  8:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 17:55 [RFC] m_can: cleanups Marc Kleine-Budde
2020-12-12 17:55 ` [can-next-rfc 1/7] can: m_can: update link to M_CAN user manual Marc Kleine-Budde
2020-12-14  8:11   ` Sean Nyekjaer [this message]
2020-12-14  8:25     ` Marc Kleine-Budde
2020-12-14  9:31   ` Oliver Hartkopp
2020-12-14  9:37     ` Marc Kleine-Budde
2020-12-14  9:55       ` Oliver Hartkopp
2020-12-14 10:10         ` Marc Kleine-Budde
2020-12-14 13:11           ` Oliver Hartkopp
2020-12-14 13:19             ` Marc Kleine-Budde
2020-12-14 13:20               ` Oliver Hartkopp
2020-12-12 17:55 ` [can-next-rfc 2/7] can: m_can: convert indention to kernel coding style Marc Kleine-Budde
2020-12-14  8:12   ` Sean Nyekjaer
2020-12-12 17:55 ` [can-next-rfc 3/7] can: m_can: use cdev as name for struct m_can_classdev uniformly Marc Kleine-Budde
2020-12-14  8:12   ` Sean Nyekjaer
2020-12-12 17:55 ` [can-next-rfc 4/7] can: m_can: m_can_config_endisable(): mark as static Marc Kleine-Budde
2020-12-14  8:12   ` Sean Nyekjaer
2020-12-12 17:55 ` [can-next-rfc 5/7] can: m_can: m_can_clk_start(): make use of pm_runtime_resume_and_get() Marc Kleine-Budde
2020-12-14  8:12   ` Sean Nyekjaer
2020-12-12 17:55 ` [can-next-rfc 6/7] can: m_can: let m_can_class_allocate_dev() allocate driver specific private data Marc Kleine-Budde
2020-12-14  8:13   ` Sean Nyekjaer
2020-12-12 17:55 ` [can-next-rfc 7/7] can: m_can: use struct m_can_classdev as drvdata Marc Kleine-Budde
2020-12-14  8:13   ` Sean Nyekjaer
2020-12-14 13:22 ` [RFC] m_can: cleanups Dan Murphy

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=c7850081-4a94-7feb-172d-c0cfe18304a8@geanix.com \
    --to=sean@geanix.com \
    --cc=dmurphy@ti.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=sriram.dash@samsung.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.