From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv3 03/10] Kconfig: Add DEPRECATED option
Date: Wed, 12 Jun 2019 09:38:36 -0400 [thread overview]
Message-ID: <20190612133836.GP7115@bill-the-cat> (raw)
In-Reply-To: <CAMty3ZBjeNREG2=0jCXWtCKSA=uvo1-jv2miB0mYEUe1OnPdPA@mail.gmail.com>
On Wed, Jun 12, 2019 at 01:03:46PM +0530, Jagan Teki wrote:
> On Thu, May 30, 2019 at 2:33 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > Add a new option, CONFIG_DEPRECATED, for code that relies on deprecated
> > functionality and has not been converted past the deadline for
> > conversion.
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > Kconfig | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/Kconfig b/Kconfig
> > index a02168690f5b..436308854d0c 100644
> > --- a/Kconfig
> > +++ b/Kconfig
> > @@ -20,6 +20,13 @@ config BROKEN
> > This option cannot be enabled. It is used as dependency
> > for broken and incomplete features.
> >
> > +config DEPRECATED
> > + bool
> > + help
> > + This option cannot be enabled. It it used as a dependency for
> > + code that relies on deprecated features that will be removed and
> > + the conversion deadline has passed.
>
> then, what would be the exact diff b/w broken vs deprecated? I do see
> same meaning in terms of code maintenance, though it is working or
> non-working.
It is a matter of human language. There was objection to using broken
as technically the code functions (and thus is not broken) but does use
deprecated APIs.
--
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/20190612/0c079c83/attachment.sig>
next prev parent reply other threads:[~2019-06-12 13:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 21:01 [U-Boot] [PATCHv3 01/10] arm: Remove zipitz2 board Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 02/10] Kconfig: Add SPI / SPI_FLASH as dependencies Tom Rini
2019-06-12 7:29 ` Jagan Teki
2019-05-29 21:01 ` [U-Boot] [PATCHv3 03/10] Kconfig: Add DEPRECATED option Tom Rini
2019-06-12 7:33 ` Jagan Teki
2019-06-12 13:38 ` Tom Rini [this message]
2019-06-12 15:45 ` Jagan Teki
2019-06-12 15:54 ` Tom Rini
2019-06-12 17:12 ` Jagan Teki
2019-05-29 21:01 ` [U-Boot] [PATCHv3 04/10] Makefile: Trigger a Warning if DEPRECATED is defined Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 05/10] Makefile: Trigger a warning for legcay spi drivers Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 06/10] spi: Kconfig: Mark MXS_SPI has DEPRECATED Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 07/10] spi: Kconfig: Mark SH_SPI as DEPRECATED Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 08/10] spi: Kconfig: Mark SOFT_SPI " Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 09/10] spi: Kconfig: Mark LPC32XX_SSP " Tom Rini
2019-05-29 21:01 ` [U-Boot] [PATCHv3 10/10] configs: Disable now unbuildable SPI options for boards Tom Rini
2019-05-29 21:33 ` Marek Vasut
2019-06-12 7:28 ` Jagan Teki
2019-05-29 22:27 ` [U-Boot] [PATCHv3 01/10] arm: Remove zipitz2 board Vasily Khoruzhick
2019-06-17 7:44 ` Jagan Teki
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=20190612133836.GP7115@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