From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mfd: max77693: Allow building as a module
Date: Fri, 8 Apr 2016 05:54:45 +0200 [thread overview]
Message-ID: <20160408035445.GA9532@kozik-lap> (raw)
In-Reply-To: <20160407132947.GB3323@x1>
On Thu, Apr 07, 2016 at 02:29:47PM +0100, Lee Jones wrote:
> On Mon, 04 Apr 2016, Krzysztof Kozlowski wrote:
>
> > The consumer of max77693 regulators on Trats2 board (samsung-usb2-phy
> > driver) supports deferred probing so the max77693 main MFD driver can be
> > built now as a module. This gives more flexibility and removes manual
> > ordering of init calls.
> >
> > Suggested-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> > Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > ---
> > drivers/mfd/Kconfig | 4 ++--
> > drivers/mfd/max77693.c | 14 ++------------
> > 2 files changed, 4 insertions(+), 14 deletions(-)
>
> I assume this can be taken immediately and doesn't depend on anything
> external to the set?
>
> For my own reference:
> Acked-by: Lee Jones <lee.jones@linaro.org>
Hi,
Yes, this can be taken as is. Only second patch (changing defconfig)
depends on this. I can take the second patch through samsung tree but
that would require a tag/branch with this... which looks like an
overkill. So maybe you would take both?
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-04-08 3:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 7:54 [PATCH 1/2] mfd: max77693: Allow building as a module Krzysztof Kozlowski
2016-04-04 7:54 ` [PATCH 2/2] ARM: multi_v7_defconfig: Switch max77693 to module Krzysztof Kozlowski
2016-04-05 14:02 ` Javier Martinez Canillas
2016-04-05 14:02 ` [PATCH 1/2] mfd: max77693: Allow building as a module Javier Martinez Canillas
2016-04-07 13:29 ` Lee Jones
2016-04-08 3:54 ` Krzysztof Kozlowski [this message]
2016-04-08 7:17 ` Lee Jones
2016-04-10 8:46 ` Krzysztof Kozlowski
2016-04-11 8:00 ` Lee Jones
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=20160408035445.GA9532@kozik-lap \
--to=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).