From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 17/27] bindings: nvmem/zii: Fix location of nvmem.txt
Date: Thu, 14 Jun 2018 17:52:11 +0100 [thread overview]
Message-ID: <c6dd6c36-2b75-cc9e-ea9e-5ee70eb656e6@linaro.org> (raw)
In-Reply-To: <fcfc83951a2997c527126af1fdd6fb1e0acbe27d.1528990947.git.mchehab+samsung@kernel.org>
On 14/06/18 17:09, Mauro Carvalho Chehab wrote:
> The location pointed there is missing "bindings/" on its path.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
> Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt b/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
> index d5e22fc67d66..0df79d9e07ec 100644
> --- a/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
> +++ b/Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
> @@ -18,7 +18,7 @@ Optional properties:
> Data cells:
>
> Data cells are child nodes of eerpom node, bindings for which are
> -documented in Documentation/bindings/nvmem/nvmem.txt
> +documented in Documentation/devicetree/bindings/nvmem/nvmem.txt
>
> Example:
>
>
next prev parent reply other threads:[~2018-06-14 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1528990947.git.mchehab+samsung@kernel.org>
2018-06-14 16:08 ` [PATCH v3 04/27] docs: fix broken references with multiple hints Mauro Carvalho Chehab
2018-06-14 16:27 ` Steven Rostedt
2018-06-14 16:08 ` [PATCH v3 05/27] docs: Fix some broken references Mauro Carvalho Chehab
2018-06-15 9:05 ` Coly Li
2018-06-14 16:09 ` [PATCH v3 16/27] docs: Fix more " Mauro Carvalho Chehab
2018-06-14 16:22 ` Guenter Roeck
2018-06-14 16:28 ` [Intel-wired-lan] " Jeff Kirsher
2018-06-14 16:29 ` [alsa-devel] " Takashi Iwai
2018-06-15 8:46 ` Matthias Brugger
2018-06-15 21:42 ` Stephen Boyd
2018-06-14 16:09 ` [PATCH v3 17/27] bindings: nvmem/zii: Fix location of nvmem.txt Mauro Carvalho Chehab
2018-06-14 16:52 ` Srinivas Kandagatla [this message]
2018-06-14 16:09 ` [PATCH v3 22/27] devicetree: fix some bindings file names Mauro Carvalho Chehab
2018-06-14 16:09 ` [PATCH v3 23/27] devicetree: fix name of pinctrl-bindings.txt Mauro Carvalho Chehab
2018-06-26 9:33 ` Linus Walleij
2018-07-03 7:33 ` Lee Jones
2018-06-14 16:09 ` [PATCH v3 24/27] devicetree: fix a series of wrong file references Mauro Carvalho Chehab
2018-06-18 7:57 ` Alexandre Torgue
2018-06-20 0:42 ` Chen-Yu Tsai
2018-07-03 7:34 ` Lee Jones
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=c6dd6c36-2b75-cc9e-ea9e-5ee70eb656e6@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).