[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0251f2c9-0f66-7dc9-7fb6-cc41a8dfd918@quicinc.com>
Date: Fri, 24 Jun 2022 11:59:25 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Paul Cercueil <paul@...pouillou.net>
CC: Arend Van Spriel <aspriel@...il.com>,
Franky Lin <franky.lin@...adcom.com>,
<linux-wireless@...r.kernel.org>,
<brcm80211-dev-list.pdl@...adcom.com>,
<SHA-cyfmac-dev-list@...ineon.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] brcmfmac: Remove #ifdef guards for PM related
functions
On 6/24/2022 11:32 AM, Paul Cercueil wrote:
> Hi,
>
> Le ven., juin 24 2022 at 09:31:22 -0700, Jeff Johnson
> <quic_jjohnson@...cinc.com> a écrit :
>> On 6/24/2022 2:24 AM, Arend Van Spriel wrote:
>>> On 6/23/2022 2:42 PM, Paul Cercueil wrote:
>>
>> [snip]
>>
>>>> - if (sdiodev->freezer) {
>>>> + if (IS_ENABLED(CONFIG_PM_SLEEP) && sdiodev->freezer) {
>>>
>>> This change is not necessary. sdiodev->freezer will be NULL when
>>> CONFIG_PM_SLEEP is not enabled.
>>
>> but won't the compiler be able to completely optimize the code away if
>> the change is present?
>
> That's correct. But do we want to complexify a bit the code for the sake
> of saving a few bytes? I leave that as an open question to the
> maintainer, I'm really fine with both options.
I'm fine either way as well. I'd have stronger opinions if ath drivers
were involved ;)
Powered by blists - more mailing lists