From: Stephen Boyd <sboyd@codeaurora.org>
To: Jiancheng Xue <xuejiancheng@hisilicon.com>
Cc: mturquette@baylibre.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
bin.chen@linaro.org, elder@linaro.org,
hermit.wangheming@hisilicon.com, yanhaifeng@hisilicon.com,
wenpan@hisilicon.com, howell.yang@hisilicon.com
Subject: Re: [PATCH 2/2] clk: hisilicon: add CRG driver for Hi3516CV300 SoC
Date: Fri, 11 Nov 2016 16:04:15 -0800 [thread overview]
Message-ID: <20161112000415.GE5177@codeaurora.org> (raw)
In-Reply-To: <1477721618-10809-3-git-send-email-xuejiancheng@hisilicon.com>
On 10/29, Jiancheng Xue wrote:
Should be a From: Pan Wen here?
> Add CRG driver for Hi3516CV300 SoC. CRG(Clock and Reset
> Generator) module generates clock and reset signals used
> by other module blocks on SoC.
>
> Signed-off-by: Pan Wen <wenpan@hisilicon.com>
And you should have signed it off? Care to resend or state that
this is incorrectly attributed to you instead of Pan Wen?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Jiancheng Xue <xuejiancheng-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
Cc: mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bin.chen-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
elder-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
hermit.wangheming-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
yanhaifeng-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
wenpan-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
howell.yang-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org
Subject: Re: [PATCH 2/2] clk: hisilicon: add CRG driver for Hi3516CV300 SoC
Date: Fri, 11 Nov 2016 16:04:15 -0800 [thread overview]
Message-ID: <20161112000415.GE5177@codeaurora.org> (raw)
In-Reply-To: <1477721618-10809-3-git-send-email-xuejiancheng-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
On 10/29, Jiancheng Xue wrote:
Should be a From: Pan Wen here?
> Add CRG driver for Hi3516CV300 SoC. CRG(Clock and Reset
> Generator) module generates clock and reset signals used
> by other module blocks on SoC.
>
> Signed-off-by: Pan Wen <wenpan-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
And you should have signed it off? Care to resend or state that
this is incorrectly attributed to you instead of Pan Wen?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-12 0:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 6:13 [PATCH 0/2] clk: hisilicon: add CRG driver for Hi3798CV200 and Hi3516CV300 SoCs Jiancheng Xue
2016-10-29 6:13 ` Jiancheng Xue
2016-10-29 6:13 ` [PATCH 1/2] clk: hisilicon: add CRG driver for Hi3798CV200 SoC Jiancheng Xue
2016-10-29 6:13 ` Jiancheng Xue
2016-11-12 0:04 ` Stephen Boyd
2016-11-12 0:04 ` Stephen Boyd
2016-10-29 6:13 ` [PATCH 2/2] clk: hisilicon: add CRG driver for Hi3516CV300 SoC Jiancheng Xue
2016-10-29 6:13 ` Jiancheng Xue
2016-10-29 11:36 ` Hao Zhang
2016-10-29 11:36 ` Hao Zhang
2016-10-31 2:05 ` Jiancheng Xue
2016-10-31 2:05 ` Jiancheng Xue
2016-11-12 0:04 ` Stephen Boyd [this message]
2016-11-12 0:04 ` Stephen Boyd
2016-11-14 1:24 ` Jiancheng Xue
2016-11-14 1:24 ` Jiancheng Xue
2016-11-14 20:03 ` Stephen Boyd
2016-11-15 1:58 ` Jiancheng Xue
2016-11-15 1:58 ` Jiancheng Xue
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=20161112000415.GE5177@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bin.chen@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=hermit.wangheming@hisilicon.com \
--cc=howell.yang@hisilicon.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=wenpan@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=yanhaifeng@hisilicon.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 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.