From: "Steven J. Hill" <Steven.Hill@cavium.com>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-mips@linux-mips.org
Cc: open list <linux-kernel@vger.kernel.org>,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH RFC 0/6] MIPS: Broadcom eXtended KSEG0/1 support
Date: Fri, 26 Jan 2018 02:31:23 -0600 [thread overview]
Message-ID: <47412287-76d7-3e39-5110-717a498e00a3@cavium.com> (raw)
In-Reply-To: <1516758426-8127-1-git-send-email-f.fainelli@gmail.com>
On 01/23/2018 07:47 PM, Florian Fainelli wrote:
[...]
>
> Florian Fainelli (6):
> MIPS: Allow board to override TLB initialization
> MIPS: Allow platforms to override mapping/unmapping coherent
> MIPS: BMIPS: Avoid referencing CKSEG1
> MIPS: Prepare for supporting eXtended KSEG0/1
> MIPS: BMIPS: Handshake with CFE
> MIPS: BMIPS: Add support for eXtended KSEG0/1 (XKS01)
>
I have tested these with your previous "MIPS: generic dma-coherence
inclusion" patchset on our Octeon III platforms with PCIe and saw
no issues. Thanks.
Steve
Tested-by: Steven J. Hill <steven.hill@cavium.com>
next prev parent reply other threads:[~2018-01-26 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 1:47 Florian Fainelli
2018-01-24 1:47 ` [PATCH RFC 1/6] MIPS: Allow board to override TLB initialization Florian Fainelli
2018-01-24 1:47 ` [PATCH RFC 2/6] MIPS: Allow platforms to override mapping/unmapping coherent Florian Fainelli
2018-01-24 1:47 ` [PATCH RFC 3/6] MIPS: BMIPS: Avoid referencing CKSEG1 Florian Fainelli
2018-02-02 17:38 ` Maciej W. Rozycki
2018-01-24 1:47 ` [PATCH RFC 4/6] MIPS: Prepare for supporting eXtended KSEG0/1 Florian Fainelli
2018-01-24 1:47 ` [PATCH RFC 5/6] MIPS: BMIPS: Handshake with CFE Florian Fainelli
2018-01-24 1:47 ` [PATCH RFC 6/6] MIPS: BMIPS: Add support for eXtended KSEG0/1 (XKS01) Florian Fainelli
2018-01-26 8:31 ` Steven J. Hill [this message]
2018-01-29 20:10 ` [PATCH RFC 0/6] MIPS: Broadcom eXtended KSEG0/1 support Florian Fainelli
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=47412287-76d7-3e39-5110-717a498e00a3@cavium.com \
--to=steven.hill@cavium.com \
--cc=david.daney@cavium.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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
all inboxes | Powered by JetHome®