From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] mmc: uniphier-sd: Use mmc_of_parse()
Date: Sat, 6 Jan 2018 20:39:48 +0100 [thread overview]
Message-ID: <24fe37ae-489a-8c0a-c142-ffd818868090@gmail.com> (raw)
In-Reply-To: <20180106192954.17753-1-marek.vasut+renesas@gmail.com>
On 01/06/2018 08:29 PM, Marek Vasut wrote:
> Drop the ad-hoc DT caps parsing in favor of common framework function.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
> Cc: Jaehoon Chung <jh80.chung@samsung.com>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Just for completeness, this all applies to u-boot/next , since the HS200
patches which are in next are needed. I'd really appreciate it if these
were applied right after that u-boot/next hits u-boot/master after
2018.01 is out .
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-01-06 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 19:29 [U-Boot] [PATCH 1/7] mmc: uniphier-sd: Use mmc_of_parse() Marek Vasut
2018-01-06 19:29 ` [U-Boot] [PATCH 2/7] mmc: uniphier-sd: Properly handle pin voltage configuration Marek Vasut
2018-01-12 9:15 ` Jaehoon Chung
2018-01-16 17:13 ` Marek Vasut
2018-01-06 19:29 ` [U-Boot] [PATCH 3/7] mmc: uniphier-sd: Add Renesas RCar quirks Marek Vasut
2018-01-06 19:29 ` [U-Boot] [PATCH 4/7] mmc: uniphier-sd: Handle Renesas div-by-1 Marek Vasut
2018-01-06 19:29 ` [U-Boot] [PATCH 5/7] mmc: uniphier-sd: Add Renesas SDR104/HS200 tuning support Marek Vasut
2018-01-06 19:29 ` [U-Boot] [PATCH 6/7] mmc: uniphier-sd: Handle DMA completion flag differences Marek Vasut
2018-01-06 19:29 ` [U-Boot] [PATCH 7/7] mmc: uniphier-sd: Always check controller version Marek Vasut
2018-01-06 19:39 ` Marek Vasut [this message]
[not found] <CGME20180116171714epcas3p3db32fc8c4d3c5b3eafd906c509d8daf2@epcas3p3.samsung.com>
2018-01-16 17:16 ` [U-Boot] [PATCH 1/7] mmc: uniphier-sd: Use mmc_of_parse() Marek Vasut
2018-01-25 1:01 ` Jaehoon Chung
2018-01-25 10:22 ` Masahiro Yamada
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=24fe37ae-489a-8c0a-c142-ffd818868090@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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