From: Wolfram Sang <wsa@the-dreams.de>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: "Simon Horman" <horms@verge.net.au>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH] arm64: dts: renesas: enable HS400 on R-Car Gen3
Date: Thu, 1 Nov 2018 20:45:29 +0100 [thread overview]
Message-ID: <20181101194528.GS2433@kunai> (raw)
In-Reply-To: <20181031233125.2800-1-niklas.soderlund@ragnatech.se>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
> 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>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-02 4:49 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 [this message]
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
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=20181101194528.GS2433@kunai \
--to=wsa@the-dreams.de \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=niklas.soderlund@ragnatech.se \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox