From: Guenter Roeck <linux@roeck-us.net>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>,
sparclinux@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iommu-common: rename iommu_pool_hash to iommu_hash_common
Date: Mon, 20 Apr 2015 00:50:19 +0000 [thread overview]
Message-ID: <55344D4B.6080603@roeck-us.net> (raw)
In-Reply-To: <b170eb1ca5dbe92a4f4dd0ac7e0c3e84a6e14464.1429458174.git.sowmini.varadhan@oracle.com>
On 04/19/2015 10:13 AM, Sowmini Varadhan wrote:
> When CONFIG_DEBUG_FORCE_WEAK_PER_CPU is set, the DEFINE_PER_CPU_SECTION
> macro will define an extern __pcpu_unique_##name variable that could
> conflict with the same definition in powerpc at this time. Avoid that
> conflict by renaming iommu_pool_hash in iommu-common.c
>
> Thanks to Guenter Roeck for catching this, and helping to test the fix.
>
> Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>,
sparclinux@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iommu-common: rename iommu_pool_hash to iommu_hash_common
Date: Sun, 19 Apr 2015 17:50:19 -0700 [thread overview]
Message-ID: <55344D4B.6080603@roeck-us.net> (raw)
In-Reply-To: <b170eb1ca5dbe92a4f4dd0ac7e0c3e84a6e14464.1429458174.git.sowmini.varadhan@oracle.com>
On 04/19/2015 10:13 AM, Sowmini Varadhan wrote:
> When CONFIG_DEBUG_FORCE_WEAK_PER_CPU is set, the DEFINE_PER_CPU_SECTION
> macro will define an extern __pcpu_unique_##name variable that could
> conflict with the same definition in powerpc at this time. Avoid that
> conflict by renaming iommu_pool_hash in iommu-common.c
>
> Thanks to Guenter Roeck for catching this, and helping to test the fix.
>
> Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2015-04-20 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 17:13 [PATCH 0/2] iommu-common build warning fixes Sowmini Varadhan
2015-04-19 17:13 ` Sowmini Varadhan
2015-04-19 17:13 ` [PATCH 1/2] iommu-common: fix x86_64 compiler warnings Sowmini Varadhan
2015-04-19 17:13 ` Sowmini Varadhan
2015-04-20 0:48 ` Guenter Roeck
2015-04-20 0:48 ` Guenter Roeck
2015-04-19 17:13 ` [PATCH 2/2] iommu-common: rename iommu_pool_hash to iommu_hash_common Sowmini Varadhan
2015-04-19 17:13 ` Sowmini Varadhan
2015-04-20 0:50 ` Guenter Roeck [this message]
2015-04-20 0:50 ` Guenter Roeck
2015-04-20 18:10 ` [PATCH 0/2] iommu-common build warning fixes David Miller
2015-04-20 18:10 ` David Miller
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=55344D4B.6080603@roeck-us.net \
--to=linux@roeck-us.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sowmini.varadhan@oracle.com \
--cc=sparclinux@vger.kernel.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.