public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Brian Masney <masneyb@onstation•org>
To: linus.walleij@linaro•org, tglx@linutronix•de, marc.zyngier@arm•com
Cc: andy.gross@linaro•org, sboyd@kernel•org,
	kernel-build-reports@lists•linaro.org,
	linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org,
	linux-arm-msm@vger•kernel.org, linux-gpio@vger•kernel.org,
	bjorn.andersson@linaro•org, linux-kernel@vger•kernel.org
Subject: [PATCH -next 1/2] genirq: export irq_chip_set_wake_parent symbol
Date: Sun,  3 Feb 2019 07:31:30 -0500	[thread overview]
Message-ID: <20190203123131.28323-1-masneyb@onstation.org> (raw)

Export the irq_chip_set_wake_parent symbol so that drivers with
hierarchical IRQ chips can be built as a module.

This fixes a build failure in linux-next's spmi-gpio when using
allmodconfig.

Signed-off-by: Brian Masney <masneyb@onstation•org>
Reported-by: Mark Brown <broonie@kernel•org>
---
See https://www.spinics.net/lists/linux-next/msg46362.html for Mark's
message.

 kernel/irq/chip.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 34e969069488..086d5a34b5a0 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -1381,6 +1381,7 @@ int irq_chip_set_wake_parent(struct irq_data *data, unsigned int on)
 
 	return -ENOSYS;
 }
+EXPORT_SYMBOL_GPL(irq_chip_set_wake_parent);
 #endif
 
 /**
-- 
2.17.2

             reply	other threads:[~2019-02-03 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 12:31 Brian Masney [this message]
2019-02-03 12:31 ` [PATCH -next 2/2] pinctrl: qcom: spmi-gpio: select IRQ_DOMAIN_HIERARCHY in Kconfig Brian Masney
2019-02-03 13:05 ` [PATCH -next 1/2] genirq: export irq_chip_set_wake_parent symbol Marc Zyngier

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=20190203123131.28323-1-masneyb@onstation.org \
    --to=masneyb@onstation$(echo .)org \
    --cc=andy.gross@linaro$(echo .)org \
    --cc=bjorn.andersson@linaro$(echo .)org \
    --cc=kernel-build-reports@lists$(echo .)linaro.org \
    --cc=linaro-kernel@lists$(echo .)linaro.org \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-arm-msm@vger$(echo .)kernel.org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=marc.zyngier@arm$(echo .)com \
    --cc=sboyd@kernel$(echo .)org \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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