From: Paul Burton <paulburton@kernel.org>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 1/2] MIPS: PCI: make phys_to_dma/dma_to_phys for pci-xtalk-bridge common
Date: Fri, 01 Nov 2019 16:27:46 -0700 [thread overview]
Message-ID: <5dbcbf73.1c69fb81.11300.7c39@mx.google.com> (raw)
In-Reply-To: <20191024101829.12543-1-tbogendoerfer@suse.de>
Hello,
Thomas Bogendoerfer wrote:
> All platforms using pci-xtalk-bridge can share common phys_to_dma/
> dma_to_phys function. So we move it form ip27 specific file to
> pci-xtalk-bridge.c
Series applied to mips-next.
> MIPS: PCI: make phys_to_dma/dma_to_phys for pci-xtalk-bridge common
> commit b9e9defb5e60
> https://git.kernel.org/mips/c/b9e9defb5e60
>
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> Signed-off-by: Paul Burton <paulburton@kernel.org>
>
> MIPS: add support for SGI Octane (IP30)
> commit 7505576d1c1a
> https://git.kernel.org/mips/c/7505576d1c1a
>
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> Signed-off-by: Paul Burton <paulburton@kernel.org>
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paulburton@kernel.org to report it. ]
prev parent reply other threads:[~2019-11-01 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 10:18 [PATCH v2 1/2] MIPS: PCI: make phys_to_dma/dma_to_phys for pci-xtalk-bridge common Thomas Bogendoerfer
2019-10-24 10:18 ` [PATCH v2 2/2] MIPS: add support for SGI Octane (IP30) Thomas Bogendoerfer
2019-11-01 23:27 ` Paul Burton [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=5dbcbf73.1c69fb81.11300.7c39@mx.google.com \
--to=paulburton@kernel.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=tbogendoerfer@suse.de \
/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).