From: Vinod Koul <vkoul@kernel.org>
To: Chen Li <chenli@uniontech.com>
Cc: Al Cooper <alcooperx@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-phy@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH] phy: usb: Fix misuse of IS_ENABLED
Date: Fri, 14 May 2021 17:41:39 +0530 [thread overview]
Message-ID: <YJ5o+2tKH1JFV1BG@vkoul-mobl.Dlink> (raw)
In-Reply-To: <87czuggpra.wl-chenli@uniontech.com>
On 27-04-21, 15:17, Chen Li wrote:
>
> While IS_ENABLED() is perfectly fine for CONFIG_* symbols, it is not
> for other symbols such as __BIG_ENDIAN that is provided directly by
> the compiler.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2021-05-14 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 7:17 [PATCH] phy: usb: Fix misuse of IS_ENABLED Chen Li
2021-04-30 15:05 ` Alan Cooper
2021-05-02 15:53 ` Florian Fainelli
2021-05-14 12:11 ` Vinod Koul [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=YJ5o+2tKH1JFV1BG@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chenli@uniontech.com \
--cc=kishon@ti.com \
--cc=linux-phy@lists.infradead.org \
/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