From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v4 00/14] Makefile: Update migration warnings
Date: Thu, 25 Mar 2021 21:24:31 +1300 [thread overview]
Message-ID: <20210325082445.519028-1-sjg@chromium.org> (raw)
The code that produces the migration warnings is quite tedious to
understanding and modify. This series updates it to use a common function
to handle the logic, so that the message definition is quite short and has
no duplication in it.
It is still necessary to write a message in migration.rst however.
This series came out of a patch intended to add an I2C warning.
It also renames CONFIG_DM_RESET; it does not need to be migrated since it
already uses driver model.
Changes in v4:
- Refactored the warning code to make it easier to get this right
- Add GPIO deprecation as well
- Add patches to rename DM_RESET to RESET
Changes in v3:
- s/'network'/I2C/ again
Changes in v2:
- s/'network'/I2C/
Simon Glass (14):
Makefile: Move non-DM migration messages to the top
Makefile: Add common code to report deprecation
Makefile: Use common code for MMC deprecation warning
Makefile: Use common code for USB deprecation warning
Makefile: Use common code for MVSATA_IDE deprecation warning
Makefile: Use common code for LIBATA deprecation warning
Makefile: Use common code for PCI deprecation warning
Makefile: Use common code for DM_VIDEO deprecation warning
Makefile: Use common code for SPI_FLASH deprecation warning
Makefile: Use common code for WDT deprecation warning
Makefile: Use common code for DM_ETH deprecation warning
Makefile: Drop the old SPI flash migration message
dm: i2c: Add a migration method for I2C
dm: gpio: Add a migration message for GPIO
Makefile | 157 +++++++++++----------------------
doc/driver-model/migration.rst | 16 ++++
2 files changed, 67 insertions(+), 106 deletions(-)
--
2.31.0.291.g576ba9dcdaf-goog
next reply other threads:[~2021-03-25 8:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 8:24 Simon Glass [this message]
2021-03-25 8:24 ` [PATCH v4 01/14] Makefile: Move non-DM migration messages to the top Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 02/14] Makefile: Add common code to report deprecation Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 03/14] Makefile: Use common code for MMC deprecation warning Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 04/14] Makefile: Use common code for USB " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 05/14] Makefile: Use common code for MVSATA_IDE " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 06/14] Makefile: Use common code for LIBATA " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 07/14] Makefile: Use common code for PCI " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 08/14] Makefile: Use common code for DM_VIDEO " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 09/14] Makefile: Use common code for SPI_FLASH " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 10/14] Makefile: Use common code for WDT " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 11/14] Makefile: Use common code for DM_ETH " Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 12/14] Makefile: Drop the old SPI flash migration message Simon Glass
2021-03-27 17:12 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 13/14] dm: i2c: Add a migration method for I2C Simon Glass
2021-03-27 17:13 ` Tom Rini
2021-03-25 8:24 ` [PATCH v4 14/14] dm: gpio: Add a migration message for GPIO Simon Glass
2021-03-27 15:58 ` Tom Rini
2021-03-27 16:05 ` Tom Rini
2021-03-31 6:46 ` [PATCH v4 00/14] Makefile: Update migration warnings Bin Meng
2021-03-31 16:39 ` Tom Rini
2021-03-31 22:19 ` Simon Glass
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=20210325082445.519028-1-sjg@chromium.org \
--to=sjg@chromium.org \
--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