public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "sboyd@codeaurora.org" <sboyd@codeaurora.org>
To: "Y.T. Tang" <andy.tang@nxp.com>
Cc: "mturquette@baylibre.com" <mturquette@baylibre.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Scott Wood <oss@buserror.net>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: qoriq-clock: Add coreclk
Date: Fri, 21 Jul 2017 15:03:23 -0700	[thread overview]
Message-ID: <20170721220323.GN19878@codeaurora.org> (raw)
In-Reply-To: <DB6PR0402MB2837EB5F759C39616BF8A904F3210@DB6PR0402MB2837.eurprd04.prod.outlook.com>

On 03/09, Y.T. Tang wrote:
> Hi Michael and Stephen,
> 
> This patch set was acked by Rob Herring. Do you have any comments on them?
> 
> BTW:  Scott should stay in author, do I need to resend them with author changed or you can change it when applying?
> 

Please resend these two patches.

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

  reply	other threads:[~2017-07-21 22:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  5:47 [PATCH 1/2] dt-bindings: qoriq-clock: Add coreclk yuantian.tang
2017-02-15  5:47 ` [PATCH 2/2] clk: qoriq: Separate root input clock for core PLLs on ls1012a yuantian.tang
2017-02-15 18:36   ` Scott Wood
2017-02-16  2:21     ` Y.T. Tang
2017-02-27  2:19 ` [PATCH 1/2] dt-bindings: qoriq-clock: Add coreclk Y.T. Tang
2017-02-27 17:18 ` Rob Herring
2017-03-01  1:45   ` Y.T. Tang
2017-03-01 23:17     ` Rob Herring
2017-03-09  8:46   ` Y.T. Tang
2017-07-21 22:03     ` sboyd [this message]
2017-07-24  1:20       ` Andy Tang

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=20170721220323.GN19878@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=andy.tang@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=oss@buserror.net \
    --cc=robh@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