All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Mike Turquette
	<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] clk: tegra: replace enum tegra114_clk by binding header
Date: Tue, 03 Sep 2013 11:57:05 -0600	[thread overview]
Message-ID: <522622F1.70008@wwwdotorg.org> (raw)
In-Reply-To: <1378213915-10222-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 09/03/2013 07:11 AM, Peter De Schrijver wrote:
> As the clock IDs are now specified in a header file, we can use those
> definitions instead of maintaining an internal enum.

Acked-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

I assume this will go through Mike's clock tree for 3.13.

I assume similar patches will follow for Tegra20/30?

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: replace enum tegra114_clk by binding header
Date: Tue, 03 Sep 2013 11:57:05 -0600	[thread overview]
Message-ID: <522622F1.70008@wwwdotorg.org> (raw)
In-Reply-To: <1378213915-10222-1-git-send-email-pdeschrijver@nvidia.com>

On 09/03/2013 07:11 AM, Peter De Schrijver wrote:
> As the clock IDs are now specified in a header file, we can use those
> definitions instead of maintaining an internal enum.

Acked-by: Stephen Warren <swarren@nvidia.com>

I assume this will go through Mike's clock tree for 3.13.

I assume similar patches will follow for Tegra20/30?

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: linux-tegra@vger.kernel.org,
	Mike Turquette <mturquette@linaro.org>,
	Joseph Lo <josephl@nvidia.com>,
	Paul Walmsley <pwalmsley@nvidia.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: replace enum tegra114_clk by binding header
Date: Tue, 03 Sep 2013 11:57:05 -0600	[thread overview]
Message-ID: <522622F1.70008@wwwdotorg.org> (raw)
In-Reply-To: <1378213915-10222-1-git-send-email-pdeschrijver@nvidia.com>

On 09/03/2013 07:11 AM, Peter De Schrijver wrote:
> As the clock IDs are now specified in a header file, we can use those
> definitions instead of maintaining an internal enum.

Acked-by: Stephen Warren <swarren@nvidia.com>

I assume this will go through Mike's clock tree for 3.13.

I assume similar patches will follow for Tegra20/30?

  parent reply	other threads:[~2013-09-03 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 13:11 [PATCH] clk: tegra: replace enum tegra114_clk by binding header Peter De Schrijver
2013-09-03 13:11 ` Peter De Schrijver
2013-09-03 13:11 ` Peter De Schrijver
     [not found] ` <1378213915-10222-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-09-03 17:57   ` Stephen Warren [this message]
2013-09-03 17:57     ` Stephen Warren
2013-09-03 17:57     ` Stephen Warren
     [not found]     ` <522622F1.70008-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-10-04 15:52       ` Peter De Schrijver
2013-10-04 15:52         ` Peter De Schrijver
2013-10-04 15:52         ` Peter De Schrijver

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=522622F1.70008@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.