lkml.org 
[lkml]   [2016]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH 4/4] gpio: zevio: make it explicitly non-modular
    From
    On Tue, May 10, 2016 at 1:59 AM, Paul Gortmaker
    <paul.gortmaker@windriver.com> wrote:

    > The Kconfig currently controlling compilation of this code is:
    >
    > drivers/gpio/Kconfig:config GPIO_ZEVIO
    > drivers/gpio/Kconfig: bool "LSI ZEVIO SoC memory mapped GPIOs"
    >
    > ...meaning that it currently is not being built as a module by anyone.
    >
    > Lets remove the modular code that is essentially orphaned, so that
    > when reading the driver there is no doubt it is builtin-only.
    >
    > We explicitly disallow a driver unbind, since that doesn't have a
    > sensible use case anyway, and it allows us to drop the ".remove"
    > code for non-modular drivers.
    >
    > Since module_platform_driver() uses the same init level priority as
    > builtin_platform_driver() the init ordering remains unchanged with
    > this commit.
    >
    > Also note that MODULE_DEVICE_TABLE is a no-op for non-modular code.
    >
    > We also delete the MODULE_LICENSE tag etc. since all that information
    > is already contained at the top of the file in the comments.
    >
    > Cc: Linus Walleij <linus.walleij@linaro.org>
    > Cc: Alexandre Courbot <gnurou@gmail.com>
    > Cc: Fabian Vogt <fabian@ritter-vogt.de>
    > Cc: linux-gpio@vger.kernel.org
    > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

    Patch applied.

    Yours,
    Linus Walleij

    \
     
     \ /
      Last update: 2016-05-11 14:01    [W:2.350 / U:0.028 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site