[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vf-9R=LLQ=AOQ3vA8uoADieOMRh1tpg2hsHTf8imnXofA@mail.gmail.com>
Date: Tue, 5 Feb 2019 17:32:44 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: "Life is hard, and then you die" <ronald@...ovation.ch>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Henrik Rydberg <rydberg@...math.org>,
Lukas Wunner <lukas@...ner.de>,
Federico Lorenzi <federico@...velground.com>,
linux-input <linux-input@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] Input: add Apple SPI keyboard and trackpad driver.
On Tue, Feb 5, 2019 at 4:21 PM Life is hard, and then you die
<ronald@...ovation.ch> wrote:
> > > +config KEYBOARD_APPLESPI
> > > + tristate "Apple SPI keyboard and trackpad"
> >
> > > + depends on (X86 && ACPI && SPI) || COMPILE_TEST
> >
> > COMPILE_TEST more or less makes sense in conjunction with architecture selection.
> > It means, your code always dependant to ACPI and SPI frameworks.
> > That's why 0day complained.
>
> Thanks. Yes, looking at this again I realized I somewhat misunderstood
> the uses of COMPILE_TEST. I've changed this now to
>
> depends on ACPI && SPI && (X86 || COMPILE_TEST)
Better to split like
depends on SPI && ACPI
depends on X86 || COMPILE_TEST
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists