linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Shailendra Singh <shailendras@nvidia.com>,
	<linuxppc-dev@lists.ozlabs.org>, <jk@ozlabs.org>,
	<shailendras@nvidia.com>, <apopple@au1.ibm.com>,
	<balbirs@au1.ibm.com>, <aritger@nvidia.com>,
	<jhubbard@nvidia.com>, <scheung@nvidia.com>,
	<amanjunatha@nvidia.com>, <jmckenna@nvidia.com>
Subject: Re: powerpc: Fix inconsistent of_node_to_nid EXPORT_SYMBOL handling
Date: Tue, 14 Feb 2017 23:40:23 +1100 (AEDT)	[thread overview]
Message-ID: <3vN27q2Kghz9s72@ozlabs.org> (raw)
In-Reply-To: <1485989562-16741-1-git-send-email-shailendras@nvidia.com>

On Wed, 2017-02-01 at 22:52:42 UTC, Shailendra Singh wrote:
> The generic implementation of of_node_to_nid is EXPORT_SYMBOL.
> 
> The powerpc implementation added by following commit is EXPORT_SYMBOL_GPL.
> commit 953039c8df7b ("[PATCH] powerpc: Allow devices to register with numa
> topology")
> 
> This creates an inconsistency for of_node_to_nid callers across
> architectures.
> 
> Update the powerpc implementation to be exported consistently with the
> generic implementation.
> 
> Signed-off-by: Shailendra Singh <shailendras@nvidia.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/be9ba9ff93cc3e44dc46da9ed25655

cheers

      parent reply	other threads:[~2017-02-14 12:40 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
2017-02-14 12:40 ` Michael Ellerman [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=3vN27q2Kghz9s72@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=amanjunatha@nvidia.com \
    --cc=apopple@au1.ibm.com \
    --cc=aritger@nvidia.com \
    --cc=balbirs@au1.ibm.com \
    --cc=jhubbard@nvidia.com \
    --cc=jk@ozlabs.org \
    --cc=jmckenna@nvidia.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scheung@nvidia.com \
    --cc=shailendras@nvidia.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).