linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: [PATCH 0/2][resend] genirq: export patches
Date: Mon, 30 Jul 2012 22:38:27 -0700 (PDT)	[thread overview]
Message-ID: <874nootrqo.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <87fw8h4xtb.wl%kuninori.morimoto.gx@renesas.com>


Hi all

These are "resend" of genirq export patches.

Kuninori Morimoto (2):
      genirq: export irq_set_chip_and_handler_name()
      genirq: export dummy_irq_chip


> 
> Hi Thomas
> 
> Could you please teach me current status of these patches ?
> 
> Kuninori Morimoto (2):
>       genirq: export irq_set_chip_and_handler_name()
>       genirq: export dummy_irq_chip
> 
> At Mon, 9 Jul 2012 22:34:23 +0200,
> Linus Walleij wrote:
> > 
> > On Mon, Jul 9, 2012 at 4:04 AM, Kuninori Morimoto
> > <kuninori.morimoto.gx@renesas.com> wrote:
> > 
> > > Hi Linus Walleij, Stephen, and Thomas
> > >
> > >> >> > After merging the gpio-lw tree, today's linux-next build (x86_64
> > >> >> > allmodconfig) failed like this:
> > >> >> >
> > >> >> > ERROR: "irq_set_chip_and_handler_name" [drivers/gpio/gpio-pcf857x.ko] undefined!
> > >> >> > ERROR: "dummy_irq_chip" [drivers/gpio/gpio-pcf857x.ko] undefined!
> > >> >>
> > >> >> Thanks, I've dropped the offending patch, Kuninori can you look into this and
> > >> >> provide a new patch? It's the second patch from your patch set.
> > >> >
> > >> > OK. I will, but it will be next week.
> > >> > And could you please show me where is your repository/branch ?
> > >>
> > >> http://git.kernel.org/?p=linux/kernel/git/linusw/linux-gpio.git;a=summary
> > >> branch devel/for-next
> > >
> > > In my check, these are export symbol issue.
> > > I think above 2 function/struct were not exported for module.
> > >
> > > Is it poosible to solve this issue by these patches ?
> > 
> > Hm Thomas has to answer to that (and merge the patches, if he
> > likes them).
> > 
> > Yours,
> > Linus Walleij
> 
> 
> Best regards
> ---
> Kuninori Morimoto

  reply	other threads:[~2012-07-31  5:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06  6:14 linux-next: build failure after merge of the gpio-lw tree Stephen Rothwell
2012-07-06  7:01 ` Linus Walleij
2012-07-06  8:55   ` Kuninori Morimoto
2012-07-08 19:14     ` Linus Walleij
2012-07-09  2:04       ` Kuninori Morimoto
2012-07-09  2:05         ` [PATCH 1/2] genirq: export irq_set_chip_and_handler_name() Kuninori Morimoto
2012-07-09  2:06         ` [PATCH 2/2] genirq: export dummy_irq_chip Kuninori Morimoto
2012-07-09 20:34         ` linux-next: build failure after merge of the gpio-lw tree Linus Walleij
2012-07-24  3:56           ` Kuninori Morimoto
2012-07-31  5:38             ` Kuninori Morimoto [this message]
2012-07-31  5:39               ` [PATCH 1/2][resend] genirq: export irq_set_chip_and_handler_name() Kuninori Morimoto
2012-08-21 16:38                 ` [tip:irq/core] genirq: Export irq_set_chip_and_handler_name() tip-bot for Kuninori Morimoto
2012-07-31  5:39               ` [PATCH 2/2][resend] genirq: export dummy_irq_chip Kuninori Morimoto
2012-08-21 16:39                 ` [tip:irq/core] genirq: Export dummy_irq_chip tip-bot for Kuninori Morimoto
2012-08-21  0:52               ` [PATCH 0/2][resend] genirq: export patches Kuninori Morimoto
2012-08-21  9:34                 ` Thomas Gleixner
2012-08-22  5:03           ` linux-next: build failure after merge of the gpio-lw tree Kuninori Morimoto
2012-08-23 21:43             ` Linus Walleij
2012-08-27  1:16               ` Kuninori Morimoto

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=874nootrqo.wl%kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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).