All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@chromium.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Mike Turquette <mturquette@linaro.org>,
	dianders@chromium.org, sonnyrao@chromium.org,
	addy.ke@rock-chips.com, hl@rock-chips.com,
	kever.yang@rock-chips.com, linux-rockchip@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] CHROMIUM: clk: rockchip: add clock IDs for the PVTM clocks
Date: Sun, 21 Dec 2014 11:34:58 -0800	[thread overview]
Message-ID: <20141221193458.GA8160@dtor-ws> (raw)
In-Reply-To: <2752828.P8uvZNT2Jv@phil>

Hi Heiko,

On Sun, Dec 21, 2014 at 03:14:53PM +0100, Heiko Stübner wrote:
> Hi Dmitry,
> 
> This looks ok and also like it's meant to go upstream, because it still has 
> the CHROMIUM-prefix?
> 
> No need to resend, I remove them myself, just want to make sure here :-)

Yes, my bad, I failed to sanitize the commit messages properly. Both of
these are meant for upstream.

Thanks!

-- 
Dmitry

  reply	other threads:[~2014-12-21 19:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19  0:13 [PATCH 1/2] CHROMIUM: clk: rockchip: add clock IDs for the PVTM clocks Dmitry Torokhov
2014-12-19  0:13 ` Dmitry Torokhov
     [not found] ` <1418948026-3463-1-git-send-email-dtor-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-12-19  0:13   ` [PATCH 2/2] CHROMIUM: clk: rockchip: add PVTM clocks on rk3288 Dmitry Torokhov
2014-12-19  0:13     ` Dmitry Torokhov
     [not found]     ` <1418948026-3463-2-git-send-email-dtor-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-12-19  0:33       ` Doug Anderson
2014-12-19  0:33         ` Doug Anderson
2014-12-19  0:33   ` [PATCH 1/2] CHROMIUM: clk: rockchip: add clock IDs for the PVTM clocks Doug Anderson
2014-12-19  0:33     ` Doug Anderson
2014-12-21 14:14   ` Heiko Stübner
2014-12-21 14:14     ` Heiko Stübner
2014-12-21 19:34     ` Dmitry Torokhov [this message]
2015-01-12 20:48   ` Heiko Stübner
2015-01-12 20:48     ` Heiko Stübner

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=20141221193458.GA8160@dtor-ws \
    --to=dtor@chromium.org \
    --cc=addy.ke@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=hl@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@linaro.org \
    --cc=sonnyrao@chromium.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 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.