From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] mmc: davinci: drop support for ti, dm6441-mmc
Date: Tue, 3 Dec 2019 23:01:53 -0500 [thread overview]
Message-ID: <20191204040153.GU15966@bill-the-cat> (raw)
In-Reply-To: <20191114151031.25309-2-brgl@bgdev.pl>
On Thu, Nov 14, 2019 at 04:10:28PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> The DM family of DaVinci SoCs is no longer supported. Drop the
> irrelevant code from the driver.
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191203/72714ed1/attachment.sig>
next prev parent reply other threads:[~2019-12-04 4:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 15:10 [U-Boot] [PATCH 0/4] omapl138_lcdk: fix MMC boot Bartosz Golaszewski
2019-11-14 15:10 ` [U-Boot] [PATCH 1/4] mmc: davinci: drop support for ti,dm6441-mmc Bartosz Golaszewski
2019-12-04 4:01 ` Tom Rini [this message]
2019-11-14 15:10 ` [U-Boot] [PATCH 2/4] mmc: davinci: drop struct davinci_mmc_plat Bartosz Golaszewski
2019-12-04 4:01 ` Tom Rini
2020-01-03 16:01 ` Adam Ford
2020-01-03 16:50 ` Bartosz Golaszewski
2020-01-03 16:59 ` Tom Rini
2020-01-03 17:26 ` Adam Ford
2019-11-14 15:10 ` [U-Boot] [PATCH 3/4] board: omapl138_lcdk: add the mmc device to SPL Bartosz Golaszewski
2019-12-04 4:02 ` Tom Rini
2019-11-14 15:10 ` [U-Boot] [PATCH 4/4] mmc: davinci: fix mmc boot in SPL Bartosz Golaszewski
2019-12-04 4:02 ` Tom Rini
2019-12-02 9:32 ` [U-Boot] [PATCH 0/4] omapl138_lcdk: fix MMC boot Bartosz Golaszewski
2019-12-02 11:54 ` Adam Ford
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=20191204040153.GU15966@bill-the-cat \
--to=trini@konsulko.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