[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87k1ud7kw4.fsf@kamboji.qca.qualcomm.com>
Date: Thu, 15 Mar 2018 11:23:07 +0200
From: Kalle Valo <kvalo@...eaurora.org>
To: Arend van Spriel <arend.vanspriel@...adcom.com>
Cc: Rafał Miłecki <rafal@...ecki.pl>,
Rafał Miłecki
<zajec5@...il.com>, Franky Lin <franky.lin@...adcom.com>,
Hante Meuleman <hante.meuleman@...adcom.com>,
Chi-Hsien Lin <chi-hsien.lin@...ress.com>,
Wright Feng <wright.feng@...ress.com>,
Pieter-Paul Giesberts <pieter-paul.giesberts@...adcom.com>,
James Hughes <james.hughes@...pberrypi.org>,
linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com,
brcm80211-dev-list@...ress.com, netdev@...r.kernel.org,
Linus Lüssing <linus.luessing@...3.blue>,
Felix Fietkau <nbd@....name>, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH] brcmfmac: drop Inter-Access Point Protocol packets by default
Arend van Spriel <arend.vanspriel@...adcom.com> writes:
> On 3/14/2018 5:10 PM, Kalle Valo wrote:
>> Rafał Miłecki <rafal@...ecki.pl> writes:
>>
>>>>> + unsigned char *eth_data = skb_mac_header(skb) + ETH_HLEN;
>>>>> +#if !defined(CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS)
>>>>
>>>> #ifndef?
>>>
>>> I followed what is used in the include/linux/etherdevice.h. Is that a
>>> good exceuse? Could it be there any some good reason for #if defined()?
>>
>> Don't know, maybe just a matter of taste? But it would be nice to know
>> the background behind #ifdef vs #if defined(), never figured it out why
>> two different forms.
>
> Well. In this case you could use either one, but if you have more
> conditions #if defined() is bit more efficient:
>
> #ifdef A
> #ifdef B
> #endif
> #endif
>
> vs.
>
> #if defined(A) && defined(B)
Oh yeah, here defined() definitely helps.
--
Kalle Valo
Powered by blists - more mailing lists