From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, PATCHv3, 4/4] dm: MIGRATION: Update migration plan for BLK
Date: Mon, 3 Dec 2018 23:49:36 -0500 [thread overview]
Message-ID: <20181204044936.GE5048@bill-the-cat> (raw)
In-Reply-To: <1543533674-8688-4-git-send-email-trini@konsulko.com>
On Thu, Nov 29, 2018 at 06:21:14PM -0500, Tom Rini wrote:
> The biggest part of migration to using CONFIG_BLK is that we need to
> have the various subsystems migrated first, so reword the plan here to
> reference the new deadlines.
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> Signed-off-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181203/a8997c79/attachment.sig>
next prev parent reply other threads:[~2018-12-04 4:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 23:21 [U-Boot] [PATCHv3 1/4] dm: MIGRATION: Add migration plan for DM_MMC Tom Rini
2018-11-29 23:21 ` [U-Boot] [PATCHv3 2/4] dm: MIGRATION: Add migration plan for DM_USB Tom Rini
2018-12-04 4:49 ` [U-Boot] [U-Boot, PATCHv3, " Tom Rini
2018-12-05 7:14 ` Stefan Roese
2018-12-05 12:23 ` Tom Rini
2018-12-07 0:05 ` Chris Packham
2018-12-07 1:19 ` Tom Rini
2018-11-29 23:21 ` [U-Boot] [PATCHv3 3/4] dm: MIGRATION: Add migration plan for CONFIG_SATA Tom Rini
2018-12-04 4:49 ` [U-Boot] [U-Boot, PATCHv3, " Tom Rini
2018-11-29 23:21 ` [U-Boot] [PATCHv3 4/4] dm: MIGRATION: Update migration plan for BLK Tom Rini
2018-12-04 4:49 ` Tom Rini [this message]
2018-11-30 8:10 ` [U-Boot] [PATCHv3 1/4] dm: MIGRATION: Add migration plan for DM_MMC Simon Goldschmidt
2018-11-30 8:50 ` Philipp Tomsich
2018-12-04 4:49 ` [U-Boot] [U-Boot, PATCHv3, " Tom Rini
2018-12-13 9:45 ` Simon Goldschmidt
2018-12-14 3:10 ` Simon Glass
2018-12-14 5:14 ` Simon Goldschmidt
2018-12-20 21:17 ` Simon Glass
2018-12-20 21:20 ` Simon Goldschmidt
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=20181204044936.GE5048@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