From: Tony Lindgren <tony@atomide.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org, Graeme Gregory <gg@slimlogic.co.uk>,
Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 11/18] mfd: tps65910: Make it explicitly non-modular
Date: Sun, 23 Dec 2018 08:35:28 -0800 [thread overview]
Message-ID: <20181223163528.GP6707@atomide.com> (raw)
In-Reply-To: <1545078688-21217-12-git-send-email-paul.gortmaker@windriver.com>
* Paul Gortmaker <paul.gortmaker@windriver.com> [181217 20:36]:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_TPS65910
> drivers/mfd/Kconfig- bool "TI TPS65910 Power Management chip"
>
> ...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.
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2018-12-23 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 20:31 [PATCH v4 00/18] mfd: demodularization of non-modular drivers Paul Gortmaker
2018-12-17 20:31 ` [PATCH 11/18] mfd: tps65910: Make it explicitly non-modular Paul Gortmaker
2018-12-23 16:35 ` Tony Lindgren [this message]
2018-12-19 8:03 ` [PATCH v4 00/18] mfd: demodularization of non-modular drivers Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2019-01-13 18:36 [PATCH v5 " Paul Gortmaker
2019-01-13 18:36 ` [PATCH 11/18] mfd: tps65910: Make it explicitly non-modular Paul Gortmaker
2018-12-07 20:10 [PATCH v3 00/18] mfd: demodularization of non-modular drivers Paul Gortmaker
2018-12-07 20:10 ` [PATCH 11/18] mfd: tps65910: Make it explicitly non-modular Paul Gortmaker
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=20181223163528.GP6707@atomide.com \
--to=tony@atomide.com \
--cc=gg@slimlogic.co.uk \
--cc=jedu@slimlogic.co.uk \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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