All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Russell Currey <ruscur@russell.cc>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/powernv: Remove support for p5ioc2
Date: Wed, 13 Jan 2016 17:39:31 +1100	[thread overview]
Message-ID: <5695F123.4070602@au1.ibm.com> (raw)
In-Reply-To: <1452665431-7880-1-git-send-email-ruscur@russell.cc>

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.

> @@ -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?

-- 
Andrew Donnellan              Software Engineer, OzLabs
andrew.donnellan@au1.ibm.com  Australia Development Lab, Canberra
+61 2 6201 8874 (work)        IBM Australia Limited

  reply	other threads:[~2016-01-13  6:40 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 [this message]
2016-01-13  6:46   ` Russell Currey
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=5695F123.4070602@au1.ibm.com \
    --to=andrew.donnellan@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ruscur@russell.cc \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.