linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: enable HS400 on R-Car Gen3
Date: Mon, 10 Dec 2018 13:10:47 +0100	[thread overview]
Message-ID: <20181210121047.en7cxcrtlgu77uxx@verge.net.au> (raw)
In-Reply-To: <20181207205204.GF17972@bigcity.dyn.berto.se>

On Fri, Dec 07, 2018 at 09:52:04PM +0100, Niklas Söderlund wrote:
> Hi Simon, Wolfram,
> 
> On 2018-12-05 22:36:13 +0100, Niklas Söderlund wrote:
> > Hi Wolfram,
> > 
> > On 2018-12-05 21:46:28 +0100, Wolfram Sang wrote:
> > > On Fri, Nov 02, 2018 at 12:57:19PM +0100, Simon Horman wrote:
> > > > On Thu, Nov 01, 2018 at 08:45:29PM +0100, Wolfram Sang wrote:
> > > > > 
> > > > > > This patch have quiet a few dependencies I'm afraid, let me know if you 
> > > > > > wish to be notified once they all upstream. I don't think it's a good 
> > > > > > idea to pick this up before all dependencies are resolved.
> > > > > 
> > > > > Yes, we should do that. Ping Simon once all dependencies are in next. It
> > > > > is still fine to have this patch here in case people want to test. BTW
> > > > > did you mention your branch somewhere where you collected all these
> > > > > patches to make HS400 working/enabled?
> > > > > 
> > > > > For this patch already:
> > > > > 
> > > > > Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > > > Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > > 
> > > > Thanks, I am marking this as deferred.
> > > > 
> > > > Please repost or ping me once the dependencies are present in
> > > > an rc release.
> > > 
> > > Niklas, are we done now, so we can ask Simon to pick up the DTS change?
> > > 
> > 
> > Almost :-)
> > 
> > I'm  waiting for Geert to take the SD quirk patches before pinging Simon 
> > to take this one. Spoke to him today about that so I hope it will not be 
> > to long.
> > 
> 
> I just confirmation that the clock patches have been pulled into 
> clk-next so this patch is ready to be consumed by you Simon.
> 
> Would it be possible to get this in this cycle or is it to late? I know 
> you wished to close your tree for v4.21 at the end of this week which it 
> technically is now ;-)

Hi Niklas,

I'm sorry but it was too late. I have queued this up for v4.22.

  reply	other threads:[~2018-12-10 12:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 23:31 [PATCH] arm64: dts: renesas: enable HS400 on R-Car Gen3 Niklas Söderlund
2018-11-01 19:45 ` Wolfram Sang
2018-11-01 19:50   ` Wolfram Sang
2018-11-02 11:57   ` Simon Horman
2018-12-05 20:46     ` Wolfram Sang
2018-12-05 21:36       ` Niklas Söderlund
2018-12-07 20:52         ` Niklas Söderlund
2018-12-10 12:10           ` Simon Horman [this message]
2018-12-18  9:07           ` Geert Uytterhoeven
2018-12-18 10:24             ` Simon Horman
2019-01-24 10:24               ` Niklas Söderlund
2019-01-25 11:16                 ` Simon Horman

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=20181210121047.en7cxcrtlgu77uxx@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).