From: Heiko Stuebner <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: fix cclk error handing
Date: Thu, 26 May 2016 23:47:39 +0200 [thread overview]
Message-ID: <1509769.ko7YVcsoMN@phil> (raw)
In-Reply-To: <1464270549-12713-1-git-send-email-zhengxing@rock-chips.com>
Am Donnerstag, 26. Mai 2016, 21:49:08 schrieb Xing Zheng:
> It maybe due to a copy-paste error the error handing should be
> cclk not clk.
>
> Reported-by: Lin Huang <lin.huang@rock-chips.com>
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
applied to my clk-fixes branch after adapting the commit message a bit.
Thanks for catching that
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: fix cclk error handing
Date: Thu, 26 May 2016 23:47:39 +0200 [thread overview]
Message-ID: <1509769.ko7YVcsoMN@phil> (raw)
In-Reply-To: <1464270549-12713-1-git-send-email-zhengxing@rock-chips.com>
Am Donnerstag, 26. Mai 2016, 21:49:08 schrieb Xing Zheng:
> It maybe due to a copy-paste error the error handing should be
> cclk not clk.
>
> Reported-by: Lin Huang <lin.huang@rock-chips.com>
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
applied to my clk-fixes branch after adapting the commit message a bit.
Thanks for catching that
Heiko
next prev parent reply other threads:[~2016-05-26 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 13:49 [PATCH] clk: rockchip: fix cclk error handing Xing Zheng
2016-05-26 13:49 ` Xing Zheng
2016-05-26 21:47 ` Heiko Stuebner [this message]
2016-05-26 21:47 ` Heiko Stuebner
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=1509769.ko7YVcsoMN@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=zhengxing@rock-chips.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.