From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH RESEND 7/7] mfd: arizona: Allow building Arizona MFD as a module
Date: Tue, 9 Feb 2016 12:38:53 +0000 [thread overview]
Message-ID: <20160209123853.GZ1490@localhost.localdomain> (raw)
In-Reply-To: <1455015123-20506-8-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Tue, Feb 09, 2016 at 10:52:03AM +0000, Charles Keepax wrote:
> There is nothing that prevents us building the Arizona MFD as a module,
> this patch enables this.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
Actually sorry drop this last patch for now, if you build the MFD
as a module then build in the other parts there are some issues.
I will need to resolve that first.
Thanks,
Charles
prev parent reply other threads:[~2016-02-09 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 10:51 [PATCH 0/7] Minor Arizona MFD Cleanups Charles Keepax
2016-02-09 10:51 ` [PATCH RESEND 1/7] mfd: wm5110: Fix defaults array based on testing Charles Keepax
2016-02-10 16:16 ` Lee Jones
2016-02-09 10:51 ` [PATCH RESEND 2/7] mfd: wm5102: " Charles Keepax
2016-02-10 16:17 ` Lee Jones
2016-02-09 10:51 ` [PATCH RESEND 3/7] mfd: wm8998: " Charles Keepax
2016-02-10 16:17 ` Lee Jones
2016-02-09 10:52 ` [PATCH RESEND 4/7] mfd: cs47l24: " Charles Keepax
2016-02-10 16:17 ` Lee Jones
2016-02-09 10:52 ` [PATCH RESEND 5/7] mfd: arizona: Remove duplicate select of MFD_CORE Charles Keepax
2016-02-10 16:18 ` Lee Jones
2016-02-09 10:52 ` [PATCH RESEND 6/7] mfd: arizona: Update small typo in Arizona SPI Kconfig Charles Keepax
2016-02-10 16:16 ` Lee Jones
2016-02-09 10:52 ` [PATCH RESEND 7/7] mfd: arizona: Allow building Arizona MFD as a module Charles Keepax
2016-02-09 12:38 ` Charles Keepax [this message]
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=20160209123853.GZ1490@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).