[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1e=-H_b8_GPJW5-uufye5_6OJ6f+ZWErjKPWkxSRSigw@mail.gmail.com>
Date: Wed, 29 Apr 2020 22:34:56 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Jerome Pouiller <Jerome.Pouiller@...abs.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jules Irenge <jbi.octave@...il.com>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: wfx: avoid compiler warning on empty array
On Wed, Apr 29, 2020 at 6:04 PM Jerome Pouiller
<Jerome.Pouiller@...abs.com> wrote:
> On Wednesday 29 April 2020 16:21:09 CEST Arnd Bergmann wrote:
> >
> > -static const struct of_device_id wfx_sdio_of_match[];
> > +static const struct of_device_id wfx_sdio_of_match[] = {
> > + { .compatible = "silabs,wfx-sdio" },
> > + { .compatible = "silabs,wf200" },
> > + { },
> > +};
> > +MODULE_DEVICE_TABLE(of, wfx_sdio_of_match);
>
> I suggest to keep the '#ifdef CONFIG_OF' around this definition. If
> CONFIG_OF is undefined, of_match_ptr() and of_match_node() will be NULL
> and it should compile.
I would generally always go for fewer #ifdef instead of more when the result
is the same. Are you worried about wasting 600 bytes of object code size for
the array on systems that need this driver but not CONFIG_OF, or something
else?
Arnd
Powered by blists - more mailing lists