From: Linus Walleij <linus.walleij@linaro.org>
To: Josh Cartwright <joshc@codeaurora.org>,
Thomas Gleixner <tglx@linutronix.de>,
Grant Likely <grant.likely@linaro.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 17 (pinctrl-msm)
Date: Tue, 25 Feb 2014 10:39:46 +0100 [thread overview]
Message-ID: <CACRpkdZbqwbknwoet_wFB8pTD4zoc5RTuU-BP9fcGefOiSJgSQ@mail.gmail.com> (raw)
In-Reply-To: <20140224184120.GB18563@joshc.qualcomm.com>
On Mon, Feb 24, 2014 at 7:41 PM, Josh Cartwright <joshc@codeaurora.org> wrote:
> On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote:
> Without too much effort, I can get this to fail just by making
> CONFIG_PINCTRL_MSM=m. handle_bad_irq isn't marked EXPORT_SYMBOL*, so
> hence the warning.
>
> Whether or not this is intentional is not clear. Do we support modules
> installing chained irq handlers?
That is a good question to tglx/Grant ...
As the kernel looks today, drivers installing chained handlers
cannot be modules, and that is it.
Yours,
Linus Walleij
prev parent reply other threads:[~2014-02-25 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 6:23 linux-next: Tree for Feb 17 Stephen Rothwell
2014-02-17 17:33 ` linux-next: Tree for Feb 17 (pinctrl-msm) Randy Dunlap
2014-02-24 14:46 ` Linus Walleij
2014-02-24 17:46 ` Bjorn Andersson
2014-02-24 18:14 ` Randy Dunlap
2014-02-24 18:41 ` Josh Cartwright
2014-02-24 18:46 ` Randy Dunlap
2014-02-24 19:28 ` Bjorn Andersson
2014-02-25 9:44 ` Linus Walleij
2014-02-25 9:39 ` Linus Walleij [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=CACRpkdZbqwbknwoet_wFB8pTD4zoc5RTuU-BP9fcGefOiSJgSQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=grant.likely@linaro.org \
--cc=joshc@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).