[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <564DF576.9010807@mleia.com>
Date: Thu, 19 Nov 2015 18:14:46 +0200
From: Vladimir Zapolskiy <vz@...ia.com>
To: "Andrew F. Davis" <afd@...com>,
Cory Tusar <cory.tusar@...1solutions.com>, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org, agust@...x.de,
gregkh@...uxfoundation.org
CC: jic23@...nel.org, broonie@...nel.org, andrew@...n.ch,
Chris.Healy@....aero, Keith.Vennel@....aero,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/5] misc: eeprom_93xx46: Implement eeprom_93xx46 DT
bindings.
Hi Andrew,
On 19.11.2015 16:00, Andrew F. Davis wrote:
> On 11/18/2015 11:50 PM, Vladimir Zapolskiy wrote:
>> Hi Cory,
>>
>> On 19.11.2015 05:29, Cory Tusar wrote:
>>> This commit implements bindings in the eeprom_93xx46 driver allowing
>>> device word size and read-only attributes to be specified via
>>> devicetree.
>>>
>>> Signed-off-by: Cory Tusar <cory.tusar@...1solutions.com>
>>> ---
[snip]
>>> +
>>> +#else
>>> +static inline int eeprom_93xx46_probe_dt(struct spi_device *spi)
>>> +{
>>> + return 0;
>>> +}
>>> +#endif
>>> +
>>
>> I actually don't see a point to have #ifdef CONFIG_OF here.
>>
>
> Usually to avoid a lot of dead code and data when OF is not enabled.
>
This is a premature optimization.
Also please see Documentation/CodingStyle, Chapter 20: Conditional
Compilation:
Wherever possible, don't use preprocessor conditionals
(#if, #ifdef) in .c files; doing so makes code harder to read
and logic harder to follow. Instead, use such conditionals in
a header file defining functions for use in those .c files,
providing no-op stub versions in the #else case, and then call
those functions unconditionally from .c files. The compiler
will avoid generating any code for the stub calls, producing
identical results, but the logic will remain easy to follow.
etc.
--
With best wishes,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists