All of lore.kernel.org
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Fix minor errors in of_clk_init() function comments
Date: Fri, 28 Mar 2014 12:07:49 -0700	[thread overview]
Message-ID: <20140328190749.5762.7875@quantum> (raw)
In-Reply-To: <1395918516-23822-1-git-send-email-s.nawrocki@samsung.com>

Quoting Sylwester Nawrocki (2014-03-27 04:08:36)
> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>

Taken into clk-next.

Thanks,
Mike

> ---
>  drivers/clk/clk.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index c859adf..29dc1e7 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -2575,7 +2575,7 @@ static int parent_ready(struct device_node *np)
>   * @matches: array of compatible values and init functions for providers.
>   *
>   * This function scans the device tree for matching clock providers
> - * and calls their initialization functions. It also do it by trying
> + * and calls their initialization functions. It also does it by trying
>   * to follow the dependencies.
>   */
>  void __init of_clk_init(const struct of_device_id *matches)
> @@ -2612,7 +2612,7 @@ void __init of_clk_init(const struct of_device_id *matches)
>                 }
>  
>                 /*
> -                * We didn't managed to initialize any of the
> +                * We didn't manage to initialize any of the
>                  * remaining providers during the last loop, so now we
>                  * initialize all the remaining ones unconditionally
>                  * in case the clock parent was not mandatory
> -- 
> 1.7.9.5
> 

      reply	other threads:[~2014-03-28 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 11:08 [PATCH] clk: Fix minor errors in of_clk_init() function comments Sylwester Nawrocki
2014-03-27 11:08 ` Sylwester Nawrocki
2014-03-28 19:07 ` 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=20140328190749.5762.7875@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.