linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Shiyan <shc_work@mail.ru>
To: linux-serial@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>, Alexander Shiyan <shc_work@mail.ru>
Subject: [PATCH 2/2] serial: max310x: Fix devicetree documentation for clock name
Date: Sat, 15 Feb 2014 14:59:02 +0400	[thread overview]
Message-ID: <1392461942-19328-2-git-send-email-shc_work@mail.ru> (raw)
In-Reply-To: <1392461942-19328-1-git-send-email-shc_work@mail.ru>

Clock names mistakenly given opposite. This patch fix this issue.

Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
---
 Documentation/devicetree/bindings/serial/maxim,max310x.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/serial/maxim,max310x.txt b/Documentation/devicetree/bindings/serial/maxim,max310x.txt
index 0daf780..83a919c 100644
--- a/Documentation/devicetree/bindings/serial/maxim,max310x.txt
+++ b/Documentation/devicetree/bindings/serial/maxim,max310x.txt
@@ -13,8 +13,8 @@ Required properties:
   controller. The format of the interrupt specifier depends on the
   parent interrupt controller.
 - clocks: phandle to the IC source clock.
-- clock-names: Should be "osc" if clock is an external crystal or
-  "xtal" if an external clock source is used.
+- clock-names: Should be "xtal" if clock is an external crystal or
+  "osc" if an external clock source is used.
 
 Optional properties:
 - gpio-controller: Marks the device node as a GPIO controller.
-- 
1.8.3.2


      reply	other threads:[~2014-02-15 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 10:59 [PATCH 1/2] serial: max310x: Fix sparse warnings Alexander Shiyan
2014-02-15 10:59 ` Alexander Shiyan [this message]

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=1392461942-19328-2-git-send-email-shc_work@mail.ru \
    --to=shc_work@mail.ru \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-serial@vger.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).