All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: devicetree@vger.kernel.org,
	"Takeshi Kihara" <takeshi.kihara.df@renesas.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	linux-arm-kernel@lists.infradead.org,
	"Marek Vasut" <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes
Date: Wed, 7 Nov 2018 20:23:45 +0100	[thread overview]
Message-ID: <20181107192345.6cq6hzpqzl6j535b@ninjato> (raw)
In-Reply-To: <f7d99456-f68f-7880-f22e-8bd47a546e82@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 243 bytes --]


> We discussed this on IRC already, which is why I need to look into that.
> The HS200 works well on the M3N though.

Can you push the branch you used somewhere? I retested the branch from
Dunbar with my M3N and it works fine with my tests.


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	devicetree@vger.kernel.org,
	"Takeshi Kihara" <takeshi.kihara.df@renesas.com>,
	"Marek Vasut" <marek.vasut+renesas@gmail.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes
Date: Wed, 7 Nov 2018 20:23:45 +0100	[thread overview]
Message-ID: <20181107192345.6cq6hzpqzl6j535b@ninjato> (raw)
In-Reply-To: <f7d99456-f68f-7880-f22e-8bd47a546e82@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]


> We discussed this on IRC already, which is why I need to look into that.
> The HS200 works well on the M3N though.

Can you push the branch you used somewhere? I retested the branch from
Dunbar with my M3N and it works fine with my tests.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes
Date: Wed, 7 Nov 2018 20:23:45 +0100	[thread overview]
Message-ID: <20181107192345.6cq6hzpqzl6j535b@ninjato> (raw)
In-Reply-To: <f7d99456-f68f-7880-f22e-8bd47a546e82@gmail.com>


> We discussed this on IRC already, which is why I need to look into that.
> The HS200 works well on the M3N though.

Can you push the branch you used somewhere? I retested the branch from
Dunbar with my M3N and it works fine with my tests.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181107/1fca0c29/attachment-0001.sig>

  reply	other threads:[~2018-11-07 19:23 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 20:46 [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes Marek Vasut
2018-11-06 20:46 ` Marek Vasut
2018-11-06 20:46 ` Marek Vasut
2018-11-07  8:50 ` Wolfram Sang
2018-11-07  8:50   ` Wolfram Sang
2018-11-07  8:50   ` Wolfram Sang
2018-11-07 10:59   ` Marek Vasut
2018-11-07 10:59     ` Marek Vasut
2018-11-07 10:59     ` Marek Vasut
2018-11-07 13:08     ` Wolfram Sang
2018-11-07 13:08       ` Wolfram Sang
2018-11-07 13:08       ` Wolfram Sang
2018-11-07 13:19       ` Marek Vasut
2018-11-07 13:19         ` Marek Vasut
2018-11-07 13:19         ` Marek Vasut
2018-11-07 19:23         ` Wolfram Sang [this message]
2018-11-07 19:23           ` Wolfram Sang
2018-11-07 19:23           ` Wolfram Sang
2018-11-07 20:35           ` Marek Vasut
2018-11-07 20:35             ` Marek Vasut
2018-11-07 20:35             ` Marek Vasut
2018-11-07 11:19 ` Simon Horman
2018-11-07 11:19   ` Simon Horman
2018-11-07 11:19   ` Simon Horman
2018-11-08 12:00 ` Geert Uytterhoeven
2018-11-08 12:00   ` Geert Uytterhoeven
2018-11-08 12:00   ` Geert Uytterhoeven
2018-11-08 13:06   ` Simon Horman
2018-11-08 13:06     ` Simon Horman
2018-11-08 13:06     ` Simon Horman
2018-11-20 10:16 ` Geert Uytterhoeven
2018-11-20 10:16   ` Geert Uytterhoeven
2018-11-20 10:16   ` Geert Uytterhoeven
2018-11-20 23:18   ` Marek Vasut
2018-11-20 23:18     ` Marek Vasut
2018-11-20 23:18     ` Marek Vasut
2018-11-21  8:39     ` Geert Uytterhoeven
2018-11-21  8:39       ` Geert Uytterhoeven
2018-11-21  8:39       ` Geert Uytterhoeven
2019-01-09 10:49 ` Simon Horman
2019-01-09 10:49   ` Simon Horman
2019-01-09 10:49   ` Simon Horman
2019-01-09 10:57   ` Wolfram Sang
2019-01-09 10:57     ` Wolfram Sang
2019-01-09 12:02     ` Marek Vasut
2019-01-09 12:02       ` Marek Vasut
2019-01-09 12:02       ` Marek Vasut
2019-01-09 12:32       ` Simon Horman
2019-01-09 12:32         ` Simon Horman
2019-01-09 12:32         ` Simon Horman
2019-01-09 12:49         ` Marek Vasut
2019-01-09 12:49           ` Marek Vasut
2019-01-09 12:49           ` Marek Vasut

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=20181107192345.6cq6hzpqzl6j535b@ninjato \
    --to=wsa@the-dreams.de \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=marek.vasut@gmail.com \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=takeshi.kihara.df@renesas.com \
    --cc=yoshihiro.shimoda.uh@renesas.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.