From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm-ccn: Fix building as a module
Date: Fri, 22 Apr 2016 09:44:48 -0700 [thread overview]
Message-ID: <7h7ffp4mpr.fsf@baylibre.com> (raw)
In-Reply-To: <571A5041.5010908@arm.com> (Suzuki K. Poulose's message of "Fri, 22 Apr 2016 17:24:33 +0100")
Suzuki K Poulose <Suzuki.Poulose@arm.com> writes:
> On 22/04/16 16:41, Kevin Hilman wrote:
>> Pawel Moll <pawel.moll@arm.com> writes:
>>
>>> On Fri, 2016-04-22 at 10:43 +0100, Suzuki K Poulose wrote:
>>>> arm-ccn driver uses irq_set_affinity, which is not exported and
>>>> hence cannot be built as a module, eventhough we have all the
>>>> bits ready. This patch makes use of the exported helper
>>>> irq_set_affinity_hint() instead. Also, the __free_irq expects
>>>> the affinity_hint to be NULL when we free the irq. So set the
>>>> affinity_hint to NULL at clean up.
>>>>
>>>> Now that we can build it as a module, update the Kconfig to
>>>> reflect the change.
>>>>
>>>> Applies on 4.6-rc4.
>>>
>>> Acked-by: Pawel Moll <pawel.moll@arm.com>
>>>
>>
>> Applied to arm-soc/fixes with Pawel's ack.
>
> Kevin,
>
> Please note that there is a change to Kconfig for ARM_CCN. So if you
> think changes to Kconfig shouldn't be pushed as a fix, by all means you
> can push this to 4.7.
>
> The title of the patch doesn't convey that. Sorry about that.
Thanks, I was just noticing that and thinking that at this stage of the
-rc, that would better wait for v4.7.
Please resumit later for v4.7
Thanks,
Kevin
prev parent reply other threads:[~2016-04-22 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 9:43 [PATCH v2] arm-ccn: Fix building as a module Suzuki K Poulose
2016-04-22 11:32 ` Pawel Moll
2016-04-22 15:41 ` Kevin Hilman
2016-04-22 16:24 ` Suzuki K Poulose
2016-04-22 16:44 ` Kevin Hilman [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=7h7ffp4mpr.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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.