linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Documentation: clk: Add locking documentation
Date: Wed, 19 Mar 2014 14:57:33 -0700	[thread overview]
Message-ID: <20140319215733.31449.47481@quantum> (raw)
In-Reply-To: <1427024.Y6pT20dv1F@avalon>

Quoting Laurent Pinchart (2014-03-12 05:11:01)
> Hello,
> 
> On Friday 28 February 2014 13:40:56 Laurent Pinchart wrote:
> > Briefly documentation the common clock framework locking scheme from a
> > clock driver point of view.
> > 
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> 
> Ping ? Is this version better (and acceptable) ?

Yes, thanks much for the resend. I fixed a small typo in the changelog:
s/documentation/document/

Taken into clk-next.

Regards,
Mike

      reply	other threads:[~2014-03-19 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 12:40 [PATCH v2] Documentation: clk: Add locking documentation Laurent Pinchart
2014-03-12 12:11 ` Laurent Pinchart
2014-03-19 21:57   ` 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=20140319215733.31449.47481@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).