linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Russell Currey <ruscur@russell.cc>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/powernv: Remove support for p5ioc2
Date: Wed, 13 Jan 2016 17:46:11 +1100	[thread overview]
Message-ID: <1452667571.1272.4.camel@russell.cc> (raw)
In-Reply-To: <5695F123.4070602@au1.ibm.com>

On Wed, 2016-01-13 at 17:39 +1100, Andrew Donnellan wrote:
> On 13/01/16 17:10, Russell Currey wrote:
> > "p5ioc2 is used by approximately 2 machines in the world, and has never
> > ever been a supported configuration."
> > 
> > The code for p5ioc2 is essentially unused and complicates what is already
> > a very complicated codebase.  Its removal is essentially a "free win" in
> > the effort to simplify the powernv PCI code.
> > 
> > In addition, support for p5ioc2 has been dropped from skiboot.  There's no
> > reason to keep it around in the kernel.
> > 
> > Signed-off-by: Russell Currey <ruscur@russell.cc>
> 
> Doesn't apply cleanly on next, but that's minor.
Going to do a V2 to address your other comment, so I might as well fix the next
issue.
> 
> > @@ -117,11 +115,6 @@ struct pnv_phb {
> > 
> >   	union {
> >   		struct {
> > -			struct iommu_table iommu_table;
> > -			struct iommu_table_group table_group;
> > -		} p5ioc2;
> > -
> > -		struct {
> >   			/* Global bridge info */
> >   			unsigned int		total_pe;
> >   			unsigned int		reserved_pe;
> 
> Given this leaves struct ioda as the only member of the union, do we 
> want to get rid of the union?
> 
Probably.  I was going to leave that for future patches (which will be a proper
refactoring rather than a pure removal), but given it makes no difference I
should just get rid of it now.

Thanks for the review.

  reply	other threads:[~2016-01-13  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  6:10 [PATCH] powerpc/powernv: Remove support for p5ioc2 Russell Currey
2016-01-13  6:39 ` Andrew Donnellan
2016-01-13  6:46   ` Russell Currey [this message]
2016-02-02  4:57 ` 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=1452667571.1272.4.camel@russell.cc \
    --to=ruscur@russell.cc \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.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).