From: Tom Rini <trini@konsulko.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
Lukasz Czechowski <lukasz.czechowski@thaumatec.com>,
u-boot@lists.denx.de, sjg@chromium.org, philipp.tomsich@vrull.eu
Subject: Re: [PATCH v3 1/4] debug_uart: Replace debug functions with dummies if CONFIG_DEBUG_UART is not set
Date: Fri, 25 Oct 2024 08:13:17 -0600 [thread overview]
Message-ID: <20241025141317.GY4959@bill-the-cat> (raw)
In-Reply-To: <076ad029-7788-4f2f-b3fe-58e61fa8cf51@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
On Fri, Oct 25, 2024 at 08:30:44PM +0800, Kever Yang wrote:
> Hi Tom,
>
> This is regression of "#ifdef CONFIG", is it possible for us to go back
> to use "#ifdef CONFIG" in this case?
Yes, that's fine, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-10-25 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 13:01 [PATCH v3 0/4] Rockchip: Allow to silent TPL/SPL debug console Lukasz Czechowski
2024-09-18 13:01 ` [PATCH v3 1/4] debug_uart: Replace debug functions with dummies if CONFIG_DEBUG_UART is not set Lukasz Czechowski
2024-09-29 1:53 ` Kever Yang
2024-09-30 8:55 ` Quentin Schulz
2024-10-25 12:30 ` Kever Yang
2024-10-25 14:13 ` Tom Rini [this message]
2024-10-25 14:27 ` Łukasz Czechowski
2024-10-25 14:56 ` Quentin Schulz
2024-10-31 9:01 ` Kever Yang
2024-11-08 9:33 ` Kever Yang
2024-11-08 20:38 ` Łukasz Czechowski
2024-11-27 2:41 ` Kever Yang
2024-11-27 22:21 ` Łukasz Czechowski
2025-01-17 16:18 ` Quentin Schulz
2025-05-05 13:53 ` Quentin Schulz
2024-09-18 13:01 ` [PATCH v3 2/4] ram: rockchip: Fix dependency of RAM_ROCKCHIP_DEBUG Lukasz Czechowski
2024-09-18 13:01 ` [PATCH v3 3/4] rockchip: px30: Weaken dependency TPL/SPL serial Lukasz Czechowski
2024-09-18 13:01 ` [PATCH v3 4/4] rockchip: px30: Fix hard dependency to DEBUG_UART_BOARD_INIT Lukasz Czechowski
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=20241025141317.GY4959@bill-the-cat \
--to=trini@konsulko.com \
--cc=kever.yang@rock-chips.com \
--cc=lukasz.czechowski@thaumatec.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=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