linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tip-bot for Sudip Mukherjee <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: lee.jones@linaro.org, tglx@linutronix.de,
	sudip.mukherjee@codethink.co.uk, sudipm.mukherjee@gmail.com,
	linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
	tony@atomide.com, m.niestroj@grinn-global.com,
	grygorii.strashko@ti.com
Subject: [tip:irq/urgent] kernel/irq: Export irq_set_parent()
Date: Fri, 21 Oct 2016 01:27:59 -0700	[thread overview]
Message-ID: <tip-3118dac501bc0317de099db81618d589503351e1@git.kernel.org> (raw)
In-Reply-To: <1475775403-27207-1-git-send-email-sudipm.mukherjee@gmail.com>

Commit-ID:  3118dac501bc0317de099db81618d589503351e1
Gitweb:     http://git.kernel.org/tip/3118dac501bc0317de099db81618d589503351e1
Author:     Sudip Mukherjee <sudipm.mukherjee@gmail.com>
AuthorDate: Thu, 6 Oct 2016 23:06:43 +0530
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Fri, 21 Oct 2016 10:21:38 +0200

kernel/irq: Export irq_set_parent()

The TPS65217 driver grew interrupt support which uses
irq_set_parent(). While it's not yet clear why this is used in the first
place, building the driver as a module fails with:

 ERROR: ".irq_set_parent" [drivers/mfd/tps65217.ko] undefined!

The correctness of the driver change is still investigated, but for now
it's less trouble to export irq_set_parent() than dealing with the build
wreckage.

[ tglx: Rewrote changelog and made the export GPL ]

Fixes: 6556bdacf646 ("mfd: tps65217: Add support for IRQs")
Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Marcin Niestroj <m.niestroj@grinn-global.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Lee Jones <lee.jones@linaro.org>
Link: http://lkml.kernel.org/r/1475775403-27207-1-git-send-email-sudipm.mukherjee@gmail.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

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

diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 0c5f1a5..9c4d304 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -721,6 +721,7 @@ int irq_set_parent(int irq, int parent_irq)
 	irq_put_desc_unlock(desc, flags);
 	return 0;
 }
+EXPORT_SYMBOL_GPL(irq_set_parent);
 #endif
 
 /*

      parent reply	other threads:[~2016-10-21  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 17:36 [PATCH] kernel: irq: fix build failure Sudip Mukherjee
2016-10-10 15:55 ` Sudip Mukherjee
2016-10-20 12:55   ` Thomas Gleixner
2016-10-21  1:00     ` Stephen Rothwell
2016-10-21  8:07       ` Thomas Gleixner
2016-10-21 10:20         ` Stephen Rothwell
2016-10-24 10:22         ` Lee Jones
2016-10-24 11:32           ` Stephen Rothwell
2016-10-24 12:08             ` Lee Jones
2016-10-21  8:27 ` tip-bot for Sudip Mukherjee [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=tip-3118dac501bc0317de099db81618d589503351e1@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=grygorii.strashko@ti.com \
    --cc=hpa@zytor.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=m.niestroj@grinn-global.com \
    --cc=mingo@kernel.org \
    --cc=sudip.mukherjee@codethink.co.uk \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tglx@linutronix.de \
    --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 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).