All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] omap1: select GENERIC_IRQ_CHIP for TI OMAP1
Date: Wed, 03 Aug 2011 10:34:36 -0700	[thread overview]
Message-ID: <8762me761f.fsf@ti.com> (raw)
In-Reply-To: <1312355897.14329.5.camel@phoenix> (Axel Lin's message of "Wed, 03 Aug 2011 15:18:17 +0800")

Hi Axel,

Axel Lin <axel.lin@gmail.com> writes:

> The gpio-omap driver has been converted to use generic IRQ chip.
> Thus select GENERIC_IRQ_CHIP for TI OMAP1 to fix below build error.
>
>  LD      vmlinux
> drivers/built-in.o: In function `omap_mpuio_alloc_gc':
> drivers/gpio/gpio-omap.c:1087: undefined reference to `irq_alloc_generic_chip'
> drivers/gpio/gpio-omap.c:1100: undefined reference to `irq_setup_generic_chip'
> drivers/built-in.o: In function `omap_gpio_show_rev':
> drivers/gpio/gpio-omap.c:998: undefined reference to `irq_gc_mask_clr_bit'
> drivers/gpio/gpio-omap.c:998: undefined reference to `irq_gc_mask_set_bit'
> make: *** [vmlinux] Error 1
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> Kevin already sent a similar patch.  http://marc.info/?l=linux-omap&m=130749135312468&w=2
> But I still have the build error with make omap1_defconfig in today's linux-next tree.
> So here is a resend.

Tony didn't pick this up for v3.1, so I now have the original in my
fixies queue for v3.1-rc, which will be posted shortly.

Sorry this has slipped through the cracks.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] omap1: select GENERIC_IRQ_CHIP for TI OMAP1
Date: Wed, 03 Aug 2011 10:34:36 -0700	[thread overview]
Message-ID: <8762me761f.fsf@ti.com> (raw)
In-Reply-To: <1312355897.14329.5.camel@phoenix> (Axel Lin's message of "Wed, 03 Aug 2011 15:18:17 +0800")

Hi Axel,

Axel Lin <axel.lin@gmail.com> writes:

> The gpio-omap driver has been converted to use generic IRQ chip.
> Thus select GENERIC_IRQ_CHIP for TI OMAP1 to fix below build error.
>
>  LD      vmlinux
> drivers/built-in.o: In function `omap_mpuio_alloc_gc':
> drivers/gpio/gpio-omap.c:1087: undefined reference to `irq_alloc_generic_chip'
> drivers/gpio/gpio-omap.c:1100: undefined reference to `irq_setup_generic_chip'
> drivers/built-in.o: In function `omap_gpio_show_rev':
> drivers/gpio/gpio-omap.c:998: undefined reference to `irq_gc_mask_clr_bit'
> drivers/gpio/gpio-omap.c:998: undefined reference to `irq_gc_mask_set_bit'
> make: *** [vmlinux] Error 1
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> Kevin already sent a similar patch.  http://marc.info/?l=linux-omap&m=130749135312468&w=2
> But I still have the build error with make omap1_defconfig in today's linux-next tree.
> So here is a resend.

Tony didn't pick this up for v3.1, so I now have the original in my
fixies queue for v3.1-rc, which will be posted shortly.

Sorry this has slipped through the cracks.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@ti.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Russell King <linux@arm.linux.org.uk>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] omap1: select GENERIC_IRQ_CHIP for TI OMAP1
Date: Wed, 03 Aug 2011 10:34:36 -0700	[thread overview]
Message-ID: <8762me761f.fsf@ti.com> (raw)
In-Reply-To: <1312355897.14329.5.camel@phoenix> (Axel Lin's message of "Wed, 03 Aug 2011 15:18:17 +0800")

Hi Axel,

Axel Lin <axel.lin@gmail.com> writes:

> The gpio-omap driver has been converted to use generic IRQ chip.
> Thus select GENERIC_IRQ_CHIP for TI OMAP1 to fix below build error.
>
>  LD      vmlinux
> drivers/built-in.o: In function `omap_mpuio_alloc_gc':
> drivers/gpio/gpio-omap.c:1087: undefined reference to `irq_alloc_generic_chip'
> drivers/gpio/gpio-omap.c:1100: undefined reference to `irq_setup_generic_chip'
> drivers/built-in.o: In function `omap_gpio_show_rev':
> drivers/gpio/gpio-omap.c:998: undefined reference to `irq_gc_mask_clr_bit'
> drivers/gpio/gpio-omap.c:998: undefined reference to `irq_gc_mask_set_bit'
> make: *** [vmlinux] Error 1
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> Kevin already sent a similar patch.  http://marc.info/?l=linux-omap&m=130749135312468&w=2
> But I still have the build error with make omap1_defconfig in today's linux-next tree.
> So here is a resend.

Tony didn't pick this up for v3.1, so I now have the original in my
fixies queue for v3.1-rc, which will be posted shortly.

Sorry this has slipped through the cracks.

Kevin

  reply	other threads:[~2011-08-03 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03  7:18 [PATCH RESEND] omap1: select GENERIC_IRQ_CHIP for TI OMAP1 Axel Lin
2011-08-03  7:18 ` Axel Lin
2011-08-03 17:34 ` Kevin Hilman [this message]
2011-08-03 17:34   ` Kevin Hilman
2011-08-03 17:34   ` Kevin Hilman

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=8762me761f.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=axel.lin@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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 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.