From: Shailendra Singh <shailendras@nvidia.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "jk@ozlabs.org" <jk@ozlabs.org>,
"apopple@au1.ibm.com" <apopple@au1.ibm.com>,
"balbirs@au1.ibm.com" <balbirs@au1.ibm.com>,
"Andy Ritger" <ARitger@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
"Sherry Cheung" <SCheung@nvidia.com>,
Aruna Manjunatha <amanjunatha@nvidia.com>,
"John McKenna" <jmckenna@nvidia.com>,
"david.daney@cavium.com" <david.daney@cavium.com>,
"robh@kernel.org" <robh@kernel.org>,
"will.deacon@arm.com" <will.deacon@arm.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: RE: [PATCH] powerpc: Fix inconsistent of_node_to_nid EXPORT_SYMBOL handling
Date: Thu, 9 Feb 2017 21:15:18 +0000 [thread overview]
Message-ID: <8d657fc33be24d45adfd9f92fdfd51b4@HQMAIL101.nvidia.com> (raw)
In-Reply-To: <87poir8slr.fsf@concordia.ellerman.id.au>
Hi Michael,
>>>Which was merged in May 2006. So the powerpc version has almost 10 yea=
rs precedence.
=20Agreed but keeping the licensing consistent will help drivers making s=
eamless use of it on all architectures.
>>> But I guess it's a pretty boring API. So I'll merge this unless anyon=
e else objects.
Thanks. Appreciate your quick response and help.
Thanks,
Shailendra
-----Original Message-----
From: Michael Ellerman [mailto:mpe@ellerman.id.au]=20
Sent: Thursday, February 09, 2017 4:19 AM
To: Shailendra Singh <shailendras@nvidia.com>; linuxppc-dev@lists.ozlabs.=
org
Cc: jk@ozlabs.org; apopple@au1.ibm.com; balbirs@au1.ibm.com; Andy Ritger =
<ARitger@nvidia.com>; John Hubbard <jhubbard@nvidia.com>; Sherry Cheung <=
SCheung@nvidia.com>; Aruna Manjunatha <amanjunatha@nvidia.com>; John McKe=
nna <jmckenna@nvidia.com>; david.daney@cavium.com; robh@kernel.org; will.=
deacon@arm.com; Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] powerpc: Fix inconsistent of_node_to_nid EXPORT_SYMB=
OL handling
Shailendra Singh <shailendras@nvidia.com> writes:
> The generic implementation of of_node_to_nid is EXPORT_SYMBOL.
True. Added in 298535c00a2c, in April 2016.
> The powerpc implementation added by following commit is EXPORT_SYMBOL_G=
PL.
> commit 953039c8df7b ("[PATCH] powerpc: Allow devices to register with=20
> numa
> topology")
Which was merged in May 2006.
So the powerpc version has almost 10 years precedence.
[Shailendra] - Agreed. Keeping the licensing consistent will help drivers=
=20making use of it on all architectures.
> This creates an inconsistency for of_node_to_nid callers across=20
> architectures.
>
> Update the powerpc implementation to be exported consistently with the =
> generic implementation.
But I guess it's a pretty boring API. So I'll merge this unless anyone el=
se objects.
[Shailendra] - Thanks. Appreciate your quick response.
cheers
> Signed-off-by: Shailendra Singh <shailendras@nvidia.com>
> Reviewed-by: Andy Ritger <aritger@nvidia.com>
> ---
> arch/powerpc/mm/numa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c index=20
> b1099cb2f393..8aa4ca3c84c9 100644
> --- a/arch/powerpc/mm/numa.c
> +++ b/arch/powerpc/mm/numa.c
> @@ -290,7 +290,7 @@ int of_node_to_nid(struct device_node *device)
> =20
> return nid;
> }
> -EXPORT_SYMBOL_GPL(of_node_to_nid);
> +EXPORT_SYMBOL(of_node_to_nid);
> =20
> static int __init find_min_common_depth(void) {
> --
> 2.4.11
-------------------------------------------------------------------------=
----------
This email message is for the sole use of the intended recipient(s) and m=
ay contain
confidential information. Any unauthorized review, use, disclosure or di=
stribution
is prohibited. If you are not the intended recipient, please contact the=
=20sender by
reply email and destroy all copies of the original message.
-------------------------------------------------------------------------=
----------
next prev parent reply other threads:[~2017-02-09 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 22:52 [PATCH] powerpc: Fix inconsistent of_node_to_nid EXPORT_SYMBOL handling Shailendra Singh
2017-02-09 12:18 ` Michael Ellerman
2017-02-09 21:15 ` Shailendra Singh [this message]
2017-02-14 12:40 ` Michael Ellerman
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=8d657fc33be24d45adfd9f92fdfd51b4@HQMAIL101.nvidia.com \
--to=shailendras@nvidia.com \
--cc=ARitger@nvidia.com \
--cc=SCheung@nvidia.com \
--cc=amanjunatha@nvidia.com \
--cc=apopple@au1.ibm.com \
--cc=arnd@arndb.de \
--cc=balbirs@au1.ibm.com \
--cc=david.daney@cavium.com \
--cc=jhubbard@nvidia.com \
--cc=jk@ozlabs.org \
--cc=jmckenna@nvidia.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=robh@kernel.org \
--cc=will.deacon@arm.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).