linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [2/3] powerpc/iommu: Cleanup setting of DMA base/offset
Date: Wed, 24 Jun 2015 09:28:07 +1000 (AEST)	[thread overview]
Message-ID: <20150623232807.64B64140319@ozlabs.org> (raw)
In-Reply-To: <1434947525.27935.27.camel@kernel.crashing.org>

On Mon, 2015-22-06 at 04:32:05 UTC, Benjamin Herrenschmidt wrote:
> Now that the table and the offset can co-exist, we no longer need
> to flip/flop, we can just establish both once at boot time.
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>  arch/powerpc/platforms/powernv/pci-ioda.c | 50 +++++++++++--------------------
>  arch/powerpc/platforms/pseries/iommu.c    |  3 +-
>  arch/powerpc/sysdev/dart_iommu.c          | 16 ++--------


This doesn't apply to my next, since the VFIO changes went in:

  Applying patch #487103 to current directory
  Description: [2/3] powerpc/iommu: Cleanup setting of DMA base/offset
  patching file arch/powerpc/platforms/powernv/pci-ioda.c
  Hunk #1 FAILED at 1621.
  Hunk #2 FAILED at 1653.
  Hunk #3 FAILED at 1841.
  Hunk #4 FAILED at 1882.
  Hunk #5 FAILED at 1977.
  5 out of 5 hunks FAILED -- saving rejects to file arch/powerpc/platforms/powernv/pci-ioda.c.rej
  patching file arch/powerpc/platforms/pseries/iommu.c
  Hunk #1 succeeded at 1253 (offset 92 lines).
  patching file arch/powerpc/sysdev/dart_iommu.c
  Hunk #1 succeeded at 313 (offset 7 lines).
  Hunk #2 succeeded at 361 (offset 7 lines).


I could fix the conflicts but then the result wouldn't have been tested.

cheers

      reply	other threads:[~2015-06-23 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  4:32 [PATCH 2/3] powerpc/iommu: Cleanup setting of DMA base/offset Benjamin Herrenschmidt
2015-06-23 23:28 ` 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=20150623232807.64B64140319@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --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).