All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] clk: tegra: Mark HCLK, SCLK and EMC as critical
Date: Mon, 12 Mar 2018 15:55:04 -0700	[thread overview]
Message-ID: <152089530498.147033.16290802622553476545@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20180312070430.GA23060@ulmo>

Quoting Thierry Reding (2018-03-12 00:04:30)
> On Fri, Mar 09, 2018 at 09:33:06AM -0800, Stephen Boyd wrote:
> > 
> > Are you going to send us a PR at some point?
> 
> Yes, I was going to let the patches cook a little in linux-next and send
> a PR by the end of the week. Does that sound okay?
> 

Perfect! Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] clk: tegra: Mark HCLK, SCLK and EMC as critical
Date: Mon, 12 Mar 2018 15:55:04 -0700	[thread overview]
Message-ID: <152089530498.147033.16290802622553476545@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20180312070430.GA23060@ulmo>

Quoting Thierry Reding (2018-03-12 00:04:30)
> On Fri, Mar 09, 2018 at 09:33:06AM -0800, Stephen Boyd wrote:
> > =

> > Are you going to send us a PR at some point?
> =

> Yes, I was going to let the patches cook a little in linux-next and send
> a PR by the end of the week. Does that sound okay?
> =


Perfect! Thanks.

  reply	other threads:[~2018-03-12 22:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 13:59 [PATCH v3 1/3] clk: tegra: Mark HCLK, SCLK and EMC as critical Dmitry Osipenko
2018-01-10 13:59 ` [PATCH v3 2/3] clk: tegra20: Correct PLL_C_OUT1 setup Dmitry Osipenko
2018-01-10 13:59 ` [PATCH v3 3/3] clk: tegra: Specify VDE clock rate Dmitry Osipenko
2018-01-15 10:56 ` [PATCH v3 1/3] clk: tegra: Mark HCLK, SCLK and EMC as critical Dmitry Osipenko
2018-03-01 13:33   ` Dmitry Osipenko
2018-03-08 14:44     ` Thierry Reding
2018-03-09 14:35       ` Dmitry Osipenko
2018-03-12  7:15         ` Thierry Reding
2018-03-12 12:37           ` Dmitry Osipenko
2018-03-12 13:48             ` Thierry Reding
2018-03-09 17:33       ` Stephen Boyd
2018-03-09 17:33         ` Stephen Boyd
2018-03-12  7:04         ` Thierry Reding
2018-03-12 22:55           ` Stephen Boyd [this message]
2018-03-12 22:55             ` Stephen Boyd

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=152089530498.147033.16290802622553476545@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=sboyd@codeaurora.org \
    --cc=thierry.reding@gmail.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.