All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: tps65910: Select REGMAP_IRQ in Kconfig to fix build error
Date: Tue, 22 Jan 2013 01:28:33 +0100	[thread overview]
Message-ID: <20130122002833.GC7409@sortiz-mobl> (raw)
In-Reply-To: <1355138096-7702-1-git-send-email-anilkumar@ti.com>

Hi Anilkumar,

On Mon, Dec 10, 2012 at 04:44:56PM +0530, AnilKumar Ch wrote:
> TPS65910 mfd driver uses functions that are only avaiable when
> REGMAP_IRQ is enabled. So "select REGMAP_IRQ" is added to mfd
> Kconfig to fix below build error:
> 
> drivers/built-in.o: In function `tps65910_irq_exit':
> /media/anil/kernel/drivers/mfd/tps65910.c:265: undefined reference to `regmap_del_irq_chip'
> drivers/built-in.o: In function `tps65910_irq_init':
> /media/anil/kernel/drivers/mfd/tps65910.c:254: undefined reference to `regmap_add_irq_chip'
> drivers/built-in.o: In function `tps65910_i2c_probe':
> /media/anil/kernel/drivers/mfd/tps65910.c:509: undefined reference to `regmap_irq_get_domain'
> make: *** [vmlinux] Error 1
> 
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
>  drivers/mfd/Kconfig |    1 +
>  1 file changed, 1 insertion(+)
Applied to my for-linus branch. Sorry for not carrying it with my 3.8 pull
request.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2013-01-22  0:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 11:14 [PATCH] mfd: tps65910: Select REGMAP_IRQ in Kconfig to fix build error AnilKumar Ch
2012-12-17  5:58 ` AnilKumar, Chimata
2013-01-02 10:15 ` AnilKumar, Chimata
2013-01-09 16:52   ` Matt Porter
2013-01-18 11:12     ` AnilKumar, Chimata
2013-01-22  0:28 ` Samuel Ortiz [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=20130122002833.GC7409@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=anilkumar@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.