From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] documentation: clk: fix couple of misspelling
Date: Wed, 20 Mar 2013 09:44:38 -0700 [thread overview]
Message-ID: <20130320164438.18043.5312@quantum> (raw)
In-Reply-To: <1362059947-3706-1-git-send-email-eduardo.valentin@ti.com>
Quoting Eduardo Valentin (2013-02-28 05:59:07)
> Correcting misspelling inside the clk.txt.
>
> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
Thanks Eduardo! Taken into clk-next.
Regards,
Mike
> ---
> Documentation/clk.txt | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/clk.txt b/Documentation/clk.txt
> index 1943fae..4274a54 100644
> --- a/Documentation/clk.txt
> +++ b/Documentation/clk.txt
> @@ -174,9 +174,9 @@ int clk_foo_enable(struct clk_hw *hw)
> };
>
> Below is a matrix detailing which clk_ops are mandatory based upon the
> -hardware capbilities of that clock. A cell marked as "y" means
> +hardware capabilities of that clock. A cell marked as "y" means
> mandatory, a cell marked as "n" implies that either including that
> -callback is invalid or otherwise uneccesary. Empty cells are either
> +callback is invalid or otherwise unnecessary. Empty cells are either
> optional or must be evaluated on a case-by-case basis.
>
> clock hardware characteristics
> --
> 1.7.7.1.488.ge8e1c
prev parent reply other threads:[~2013-03-20 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 13:59 [PATCH 1/1] documentation: clk: fix couple of misspelling Eduardo Valentin
2013-03-20 16:44 ` Mike Turquette [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=20130320164438.18043.5312@quantum \
--to=mturquette@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).