public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: <Nicolas.Ferre@microchip.com>
To: <corbet@lwn.net>, <linux-doc@vger.kernel.org>
Cc: <linux-arch@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<dmitry.torokhov@gmail.com>, <wens@csie.org>,
	<jernej.skrabec@gmail.com>, <samuel@sholland.org>,
	<thierry.reding@gmail.com>, <u.kleine-koenig@pengutronix.de>,
	<gregkh@linuxfoundation.org>, <linux-input@vger.kernel.org>,
	<linux-sunxi@lists.linux.dev>, <linux-pwm@vger.kernel.org>,
	<linux-serial@vger.kernel.org>
Subject: Re: [PATCH v2 6/7] docs: update some straggling Documentation/arm references
Date: Tue, 30 May 2023 07:20:18 +0000	[thread overview]
Message-ID: <b4dac802-f600-6459-1f4a-241a62676fdd@microchip.com> (raw)
In-Reply-To: <20230529144856.102755-7-corbet@lwn.net>

On 29/05/2023 at 16:48, Jonathan Corbet wrote:
> diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm/pwm-atmel.c
> index 0c567d9623cd..5f7d286871cf 100644
> --- a/drivers/pwm/pwm-atmel.c
> +++ b/drivers/pwm/pwm-atmel.c
> @@ -6,7 +6,7 @@
>    *              Bo Shen<voice.shen@atmel.com>
>    *
>    * Links to reference manuals for the supported PWM chips can be found in
> - * Documentation/arm/microchip.rst.
> + * Documentation/arch/arm/microchip.rst.
>    *
>    * Limitations:
>    * - Periods start with the inactive level.

For Microchip changes:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>

Thanks Jonathan. Best regards,
   Nicolas

-- 
Nicolas Ferre

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

  parent reply	other threads:[~2023-05-30  7:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 14:48 [PATCH v2 0/7] docs: Move Documentation/arm under Documentation/arch Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 1/7] arm: docs: Move Arm documentation to Documentation/arch/ Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 2/7] arm: update in-source documentation references Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 3/7] arm64: Update Documentation/arm references Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 4/7] mips: update a reference to a moved Arm Document Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 5/7] crypto: update some Arm documentation references Jonathan Corbet
2023-05-31 21:22   ` Jernej Škrabec
2023-05-29 14:48 ` [PATCH v2 6/7] docs: update some straggling Documentation/arm references Jonathan Corbet
2023-05-29 14:57   ` Greg Kroah-Hartman
2023-05-30  7:20   ` Nicolas.Ferre [this message]
2023-05-31 21:23   ` Jernej Škrabec
2023-06-14  7:04   ` Uwe Kleine-König
2023-05-29 14:48 ` [PATCH v2 7/7] dt-bindings: Update " Jonathan Corbet
2023-06-07 20:55   ` Rob Herring

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=b4dac802-f600-6459-1f4a-241a62676fdd@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=corbet@lwn.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=samuel@sholland.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wens@csie.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