From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Otto Sabart <ottosabart@seberm.com>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
Lee Jones <lee.jones@linaro.org>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: Re: [PATCH 1/1] doc: pinctrl: fix bad reference to pinctrl.txt file
Date: Thu, 10 Jan 2019 09:32:44 +0000 [thread overview]
Message-ID: <4338fca9-11ca-ec92-e6bf-a5734eb1c07c@opensource.cirrus.com> (raw)
In-Reply-To: <10552cb9ce3067c4b4cf8c25ed6a20c498478549.1547060185.git.ottosabart@seberm.com>
On 09/01/19 19:06, Otto Sabart wrote:
> The pinctrl.txt file was converted into reStructuredText and moved into
> driver-api folder. This patch updates the broken reference.
>
> Fixes: 5a9b73832e9e ("pinctrl.txt: move it to the driver-api book")
> Signed-off-by: Otto Sabart <ottosabart@seberm.com>
> ---
> include/linux/mfd/madera/pdata.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/mfd/madera/pdata.h b/include/linux/mfd/madera/pdata.h
> index 8dc852402dbb..dd00ab824e5b 100644
> --- a/include/linux/mfd/madera/pdata.h
> +++ b/include/linux/mfd/madera/pdata.h
> @@ -34,7 +34,8 @@ struct madera_codec_pdata;
> * @micvdd: Substruct of pdata for the MICVDD regulator
> * @irq_flags: Mode for primary IRQ (defaults to active low)
> * @gpio_base: Base GPIO number
> - * @gpio_configs: Array of GPIO configurations (See Documentation/pinctrl.txt)
> + * @gpio_configs: Array of GPIO configurations (See
> + * Documentation/driver-api/pinctl.rst)
> * @n_gpio_configs: Number of entries in gpio_configs
> * @gpsw: General purpose switch mode setting. Depends on the external
> * hardware connected to the switch. (See the SW1_MODE field
>
Acked-by: Richard Fitzgerald <rf@opensource.cirrus.com>
next prev parent reply other threads:[~2019-01-10 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 19:06 Otto Sabart
2019-01-10 9:32 ` Richard Fitzgerald [this message]
2019-01-18 11:55 ` Charles Keepax
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=4338fca9-11ca-ec92-e6bf-a5734eb1c07c@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=ottosabart@seberm.com \
--cc=patches@opensource.cirrus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome