From: Ingo Molnar <mingo@kernel.org>
To: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
dougthompson@xmission.com, bp@alien8.de, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH] x86/amd_nb: Rename amd_get_node_id
Date: Wed, 14 Oct 2015 15:42:49 +0200 [thread overview]
Message-ID: <20151014134249.GB10316@gmail.com> (raw)
In-Reply-To: <1444742394-3974-1-git-send-email-Aravind.Gopalakrishnan@amd.com>
* Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com> wrote:
> This function doesn't give us the "Node ID" as the function
> name suggests. Rather- it receives a PCI device as argument,
> checks the available F3 PCI device IDs in the system
> and returns the index of the matching Bus/Device IDs
>
> Renaming it accordingly in this patch.
> No functional change is introduced.
>
> Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> ---
> arch/x86/include/asm/amd_nb.h | 2 +-
> drivers/edac/amd64_edac.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/include/asm/amd_nb.h b/arch/x86/include/asm/amd_nb.h
> index 1a5da2e..319843d 100644
> --- a/arch/x86/include/asm/amd_nb.h
> +++ b/arch/x86/include/asm/amd_nb.h
> @@ -81,7 +81,7 @@ static inline struct amd_northbridge *node_to_amd_nb(int node)
> return (node < amd_northbridges.num) ? &amd_northbridges.nb[node] : NULL;
> }
>
> -static inline u16 amd_get_node_id(struct pci_dev *pdev)
> +static inline u16 amd_get_node_id_from_pci_dev(struct pci_dev *pdev)
So if we go to the trouble of naming things properly, I guess that function should
be named:
amd_pci_dev_to_node_id()
or so.
Thanks,
Ingo
next prev parent reply other threads:[~2015-10-14 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:19 Aravind Gopalakrishnan
2015-10-14 13:42 ` Ingo Molnar [this message]
2015-10-14 13:51 ` Borislav Petkov
2015-10-14 14:48 ` Aravind Gopalakrishnan
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=20151014134249.GB10316@gmail.com \
--to=mingo@kernel.org \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome