From: Greg KH <gregkh@linuxfoundation.org>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: sameo@linux.intel.com, broonie@opensource.wolfsonmicro.com,
dan.carpenter@oracle.com, rdunlap@xenotime.net,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-omap@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mfd/regulator: tps65217: Move regulator plat data handling to regulator
Date: Mon, 13 Aug 2012 08:23:54 -0700 [thread overview]
Message-ID: <20120813152354.GB5745@kroah.com> (raw)
In-Reply-To: <1344870365-11645-1-git-send-email-anilkumar@ti.com>
On Mon, Aug 13, 2012 at 08:36:05PM +0530, AnilKumar Ch wrote:
> Regulator platform data handling was mistakenly added to MFD
> driver. So we will see build errors if we compile MFD drivers
> without CONFIG_REGULATOR. This patch moves regulator platform
> data handling from TPS65217 MFD driver to regulator driver.
>
> This makes MFD driver independent of REGULATOR framework so
> build error is fixed if CONFIG_REGULATOR is not set.
>
> drivers/built-in.o: In function `tps65217_probe':
> tps65217.c:(.devinit.text+0x13e37): undefined reference
> to `of_regulator_match'
>
> This patch also fix allocation size of tps65217 platform data.
> Current implementation allocates a struct tps65217_board for each
> regulator specified in the device tree. But the structure itself
> provides array of regulators so one instance of it is sufficient.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> This patch is tested on BeagleBone with regulator device node
> additions. And this is based on mfd/master.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2012-08-13 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 15:06 [PATCH v2] mfd/regulator: tps65217: Move regulator plat data handling to regulator AnilKumar Ch
2012-08-13 15:23 ` Greg KH [this message]
2012-08-14 4:22 ` AnilKumar, Chimata
2012-08-22 9:02 ` Samuel Ortiz
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=20120813152354.GB5745@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anilkumar@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).