From: Tom Rini <trini@konsulko.com>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Joe Hershberger <joe.hershberger@ni.com>,
Lukasz Majewski <lukma@denx.de>, Marek Vasut <marex@denx.de>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Ramon Fried <rfried.dev@gmail.com>,
Roman Stratiienko <r.stratiienko@gmail.com>,
Sean Anderson <seanga2@gmail.com>, Simon Glass <sjg@chromium.org>,
Stefan Roese <sr@denx.de>,
U-Boot STM32 <uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] fastboot: remove #ifdef CONFIG when it is possible
Date: Thu, 12 Jan 2023 10:18:32 -0500 [thread overview]
Message-ID: <20230112151832.GE3787616@bill-the-cat> (raw)
In-Reply-To: <20221215101547.1.Ic4654626494193d6dd4788d14fda0aae447783a5@changeid>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On Thu, Dec 15, 2022 at 10:15:50AM +0100, Patrick Delaunay wrote:
> Much of the fastboot code predates the introduction of Kconfig and
> has quite a few #ifdefs in it which is unnecessary now that we can use
> IS_ENABLED() et al.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> Reviewed-by: Sean Anderson <sean.anderson@seco.com>
> Tested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> # on vim3l
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-01-12 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:15 [PATCH] fastboot: remove #ifdef CONFIG when it is possible Patrick Delaunay
2022-12-15 13:45 ` Mattijs Korpershoek
2022-12-16 7:50 ` Mattijs Korpershoek
2022-12-15 14:30 ` Marek Vasut
2022-12-15 15:37 ` Sean Anderson
2022-12-15 15:40 ` Sean Anderson
2023-01-03 12:39 ` Patrick DELAUNAY
2023-01-03 20:35 ` Tom Rini
2023-01-05 11:37 ` Patrick DELAUNAY
2023-01-06 14:31 ` Tom Rini
2023-01-12 15:18 ` Tom Rini [this message]
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=20230112151832.GE3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=joe.hershberger@ni.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=mkorpershoek@baylibre.com \
--cc=patrick.delaunay@foss.st.com \
--cc=r.stratiienko@gmail.com \
--cc=rfried.dev@gmail.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.com \
--cc=xypron.glpk@gmx.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