From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Lee Jones <lee.jones@linaro.org>
Subject: [RFC/RFT PATCH 0/2] mfd: max14577: Allow the driver to be built as a module
Date: Wed, 16 Mar 2016 13:48:48 -0300 [thread overview]
Message-ID: <1458146930-2723-1-git-send-email-javier@osg.samsung.com> (raw)
Hello,
This series is similar to [0] and allows the max14577 PMIC MFD driver to
be built as a module. Currently the Kconfig symbol for the driver is a
boolean but there isn't really a reason for this restriction.
The patches have been just built tested because I don't have any of the
boards using this driver, so testing will be highly appreciated.
[0]: https://lkml.org/lkml/2016/2/11/857
Best regards,
Javier
Javier Martinez Canillas (2):
mfd: max14577: Use module_init() instead of subsys_initcall()
mfd: max14577: Allow driver to be built as a module
drivers/mfd/Kconfig | 4 ++--
drivers/mfd/max14577.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-16 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 16:48 Javier Martinez Canillas [this message]
2016-03-16 16:48 ` [RFC/RFT PATCH 1/2] mfd: max14577: Use module_init() instead of subsys_initcall() Javier Martinez Canillas
2016-03-16 16:48 ` [RFC/RFT PATCH 2/2] mfd: max14577: Allow driver to be built as a module Javier Martinez Canillas
2016-03-17 1:58 ` Chanwoo Choi
2016-03-17 15:37 ` Javier Martinez Canillas
2016-03-17 16:57 ` Javier Martinez Canillas
2016-03-17 18:02 ` Javier Martinez Canillas
2016-03-18 7:55 ` Chanwoo Choi
2016-03-18 10:50 ` Javier Martinez Canillas
2016-03-17 1:09 ` [RFC/RFT PATCH 0/2] mfd: max14577: Allow the " Krzysztof Kozlowski
2016-03-17 15:22 ` Javier Martinez Canillas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1458146930-2723-1-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=cw00.choi@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®