From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: paulus@samba.org, nfont@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2 v2] powerpc/iommu: Remove the dependency on EEH struct in DDW mechanism
Date: Wed, 6 Apr 2016 22:55:31 -0300 [thread overview]
Message-ID: <5705BE13.6030105@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160407004833.GB16777@gwshan>
On 04/06/2016 09:48 PM, Gavin Shan wrote:
> On Wed, Apr 06, 2016 at 09:20:05PM -0300, Guilherme G. Piccoli wrote:
>> Fixes: 39baadbf36ce ("powerpc/eeh: Remove eeh information from pci_dn")
>> Signed-off-by: Guilherme G. Piccoli <gpiccoli@linux.vnet.ibm.com>
>
> Reviewed-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>
> Thanks, Guilherme. Please make sure if it needs to be backported
> to stable kernel. I assume it probably needs to be in 3.10+.
Thanks for your quick review Gavin! I guess we only need to backport
this to kernels containing 39baadbf36ce. Stable is a good idea.
>> + dn = pci_device_to_OF_node(dev);
>> + pdn = PCI_DN(dn);
>> + cfg_addr = (pdn->busno << 8) | (pdn->devfn);
>> + buid = pdn->phb->buid;
>
> No parentheses required on the second operand when getting @cfg_addr.
> It would be nicer to initialize @buid and then @cfg_addr. When
> developers look at the code, they usually check @buid and then
> @cfg_addr.
OK, I'll change this in v3. buid first, cfg_addr second. Also I'll
remove the parentheses - it's a bad habit of mine =)
Cheers,
Guilherme
next prev parent reply other threads:[~2016-04-07 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 0:20 [PATCH 1/2 v2] Revert "powerpc/eeh: Fix crash in eeh_add_device_early() on Cell" Guilherme G. Piccoli
2016-04-07 0:20 ` [PATCH 2/2 v2] powerpc/iommu: Remove the dependency on EEH struct in DDW mechanism Guilherme G. Piccoli
2016-04-07 0:48 ` Gavin Shan
2016-04-07 1:55 ` Guilherme G. Piccoli [this message]
2016-04-07 0:35 ` [PATCH 1/2 v2] Revert "powerpc/eeh: Fix crash in eeh_add_device_early() on Cell" Gavin Shan
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=5705BE13.6030105@linux.vnet.ibm.com \
--to=gpiccoli@linux.vnet.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).