All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: YueHaibing <yuehaibing@huawei.com>
Cc: jason@lakedaemon.net, maz@kernel.org, paul@crapouillou.net,
	malat@debian.org, paul.burton@mips.com,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH] irqchip/irq-ingenic-tcu: Fix COMPILE_TEST building
Date: Fri, 16 Aug 2019 14:28:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1908161428001.8238@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190813015602.30576-1-yuehaibing@huawei.com>

On Tue, 13 Aug 2019, YueHaibing wrote:

> While do COMPILE_TEST building, if GENERIC_IRQ_CHIP is
> not selected, it fails:
> 
> drivers/irqchip/irq-ingenic-tcu.o: In function `ingenic_tcu_intc_cascade':
> irq-ingenic-tcu.c:(.text+0x13f): undefined reference to `irq_get_domain_generic_chip'
> drivers/irqchip/irq-ingenic-tcu.o: In function `ingenic_tcu_irq_init':
> irq-ingenic-tcu.c:(.init.text+0x97): undefined reference to `irq_generic_chip_ops'
> irq-ingenic-tcu.c:(.init.text+0xdd): undefined reference to `__irq_alloc_domain_generic_chips'
> irq-ingenic-tcu.c:(.init.text+0x10b): undefined reference to `irq_get_domain_generic_chip'
> 
> select GENERIC_IRQ_CHIP to fix this.
> 
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Fixes: 9536eba03ec7 ("irqchip: Add irq-ingenic-tcu driver")

git show 9536eba03ec7

fatal: ambiguous argument '9536eba03ec7': unknown revision or path not in
       the working tree.

Thanks,

	tglx

  reply	other threads:[~2019-08-16 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13  1:56 [PATCH] irqchip/irq-ingenic-tcu: Fix COMPILE_TEST building YueHaibing
2019-08-16 12:28 ` Thomas Gleixner [this message]
2019-08-16 20:19   ` Paul Burton
2019-08-16 20:41     ` Thomas Gleixner
2019-08-19 21:17 ` Paul Burton

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=alpine.DEB.2.21.1908161428001.8238@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=malat@debian.org \
    --cc=maz@kernel.org \
    --cc=paul.burton@mips.com \
    --cc=paul@crapouillou.net \
    --cc=yuehaibing@huawei.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.