From: James Hogan <jhogan@kernel.org>
To: David Daney <david.daney@cavium.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-kernel@vger.kernel.org,
"Steven J. Hill" <steven.hill@cavium.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Carlos Munoz <cmunoz@cavium.com>
Subject: Re: [PATCH v8 4/4] MIPS: Octeon: Add a global resource manager.
Date: Fri, 2 Mar 2018 14:54:50 +0000 [thread overview]
Message-ID: <20180302145449.GB4197@saruman> (raw)
In-Reply-To: <20180222230716.21442-5-david.daney@cavium.com>
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
On Thu, Feb 22, 2018 at 03:07:16PM -0800, David Daney wrote:
> From: Carlos Munoz <cmunoz@cavium.com>
>
> Add a global resource manager to manage tagged pointers within
> bootmem allocated memory. This is used by various functional
> blocks in the Octeon core like the FPA, Ethernet nexus, etc.
>
> Signed-off-by: Carlos Munoz <cmunoz@cavium.com>
> Signed-off-by: Steven J. Hill <Steven.Hill@cavium.com>
> Signed-off-by: David Daney <david.daney@cavium.com>
Acked-by: James Hogan <jhogan@kernel.org>
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-02 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 23:07 [PATCH v8 0/4] Prerequisites for Cavium OCTEON-III network driver David Daney
2018-02-22 23:07 ` [PATCH v8 1/4] MIPS: Octeon: Enable LMTDMA/LMTST operations David Daney
2018-02-22 23:07 ` [PATCH v8 2/4] MIPS: Octeon: Automatically provision CVMSEG space David Daney
2018-03-02 14:10 ` James Hogan
2018-02-22 23:07 ` [PATCH v8 3/4] staging: octeon: Remove USE_ASYNC_IOBDMA macro David Daney
2018-02-22 23:07 ` [PATCH v8 4/4] MIPS: Octeon: Add a global resource manager David Daney
2018-03-02 14:54 ` James Hogan [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=20180302145449.GB4197@saruman \
--to=jhogan@kernel.org \
--cc=cmunoz@cavium.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=steven.hill@cavium.com \
/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).