All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [gpio:for-next 9/33] ERROR: "irq_set_chip_and_handler_name" [drivers/gpio/gpio-pcf857x.ko] undef
Date: Fri, 14 Sep 2012 04:18:26 +0000	[thread overview]
Message-ID: <20120914041826.GA14274@localhost> (raw)
In-Reply-To: <20120914035026.GA14169@localhost>

On Thu, Sep 13, 2012 at 09:10:20PM -0700, Kuninori Morimoto wrote:
> 
> Hi Fengguang
> 
> Thank you for contacting me
> 
> > FYI, kernel build failed on
> > 
> > tree:   git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
> > head:   c9bcf5cde5267509957099558f00400ede028cc5
> > commit: 6e20a0a429bd4dc07d6de16d9c247270e04e4aa0 [9/33] gpio: pcf857x: enable gpio_to_irq() support
> > config: x86_64-randconfig-s313 (attached as .config)
> > 
> > All related error/warning messages:
> > 
> > ERROR: "irq_set_chip_and_handler_name" [drivers/gpio/gpio-pcf857x.ko] undefined!
> > ERROR: "dummy_irq_chip" [drivers/gpio/gpio-pcf857x.ko] undefined!
> 
> I believe this issue was solved by these patches
> 
>   http://git.kernel.org/tip/17d83127d4c2b322dd8f217e0ac08c66eb403779
>   http://git.kernel.org/tip/b3ae66f209e8929db62b5a5f874ab2cdcf5ef1d4
> 
> These are accepted by Thomas

OK. Sorry I just added the gpio tree to auto build tests and it seems
the system is currently working on the old commits..

Thanks,
Fengguang

      parent reply	other threads:[~2012-09-14  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  3:50 [gpio:for-next 9/33] ERROR: "irq_set_chip_and_handler_name" [drivers/gpio/gpio-pcf857x.ko] undefined Fengguang Wu
2012-09-14  4:10 ` [gpio:for-next 9/33] ERROR: "irq_set_chip_and_handler_name" [drivers/gpio/gpio-pcf857x.ko] undef Kuninori Morimoto
2012-09-14  4:18 ` Fengguang Wu [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=20120914041826.GA14274@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@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.