linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Ray Jui <rjui@broadcom.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	Simran Rai <ssimran@broadcom.com>
Subject: Re: [PATCH RESEND v2 1/4] Documentation: dt-bindings: Add DT bindings for Cygnus audio clock
Date: Fri, 29 Jan 2016 16:33:22 -0800	[thread overview]
Message-ID: <20160130003321.GC12841@codeaurora.org> (raw)
In-Reply-To: <1453857521-8804-2-git-send-email-rjui@broadcom.com>

On 01/26, Ray Jui wrote:
> From: Simran Rai <ssimran@broadcom.com>
> 
> This patch adds audio clock device tree binding documentation to an
> existing Cygnus clock DT bindings document.
> 
> Signed-off-by: Simran Rai <ssimran@broadcom.com>
> Reviewed-by: Ray Jui <rjui@broadcom.com>
> Reviewed-by: Lori Hikichi <lhikichi@broadcom.com>
> Reviewed-by: Scott Branden <sbranden@broadcom.com>
> ---

Applied to clk-iproc

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-01-30  0:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  1:18 [PATCH RESEND v2 0/4] Add Cygnus audio clock support Ray Jui
2016-01-27  1:18 ` [PATCH RESEND v2 1/4] Documentation: dt-bindings: Add DT bindings for Cygnus audio clock Ray Jui
2016-01-30  0:33   ` Stephen Boyd [this message]
2016-01-27  1:18 ` [PATCH RESEND v2 2/4] clk: iproc: Add support for Cygnus audio clocks Ray Jui
2016-01-30  0:33   ` Stephen Boyd
2016-01-27  1:18 ` [PATCH RESEND v2 3/4] clk: iproc: Remove __init from header Ray Jui
2016-01-30  0:33   ` Stephen Boyd
2016-01-27  1:18 ` [PATCH RESEND v2 4/4] ARM: dts: enable audio clock support for Cygnus Ray Jui
2016-01-30  0:42   ` Ray Jui
2016-02-01  0:24     ` Florian Fainelli

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=20160130003321.GC12841@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rjui@broadcom.com \
    --cc=ssimran@broadcom.com \
    /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).