From: Catalin Marinas <catalin.marinas@arm.com>
To: Roy Pledge <roy.pledge@nxp.com>
Cc: leoyang.li@nxp.com, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, arnd@arndb.de, madalin.bucur@nxp.com,
linux@armlinux.org.uk, oss@buserror.net
Subject: Re: [v5 03/12] soc/fsl/qbman: Use shared-dma-pool for QMan private memory allocations
Date: Thu, 21 Sep 2017 15:30:30 +0100 [thread overview]
Message-ID: <20170921143030.d6qafcrn4sy5bpap@localhost> (raw)
In-Reply-To: <1505767187-4596-4-git-send-email-roy.pledge@nxp.com>
On Mon, Sep 18, 2017 at 04:39:38PM -0400, Roy Pledge wrote:
> Use the shared-memory-pool mechanism for frame queue descriptor and
> packed frame descriptor record area allocations.
>
> Signed-off-by: Roy Pledge <roy.pledge@nxp.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2017-09-21 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 20:39 [v5 00/12] soc/fsl/qbman: Enable QBMan on ARM Platforms Roy Pledge
2017-09-18 20:39 ` [v5 03/12] soc/fsl/qbman: Use shared-dma-pool for QMan private memory allocations Roy Pledge
2017-09-21 14:30 ` Catalin Marinas [this message]
2017-09-18 20:39 ` [v5 04/12] dt-bindings: soc/fsl: Update reserved memory binding for QBMan Roy Pledge
[not found] ` <1505767187-4596-5-git-send-email-roy.pledge-3arQi8VN3Tc@public.gmane.org>
2017-09-21 18:36 ` Leo Li
2017-09-21 23:14 ` Rob Herring
2017-09-18 20:39 ` [v5 05/12] soc/fsl/qbman: Drop set/clear_bits usage Roy Pledge
[not found] ` <1505767187-4596-6-git-send-email-roy.pledge-3arQi8VN3Tc@public.gmane.org>
2017-09-21 14:31 ` Catalin Marinas
2017-09-18 20:39 ` [v5 06/12] soc/fsl/qbman: Drop L1_CACHE_BYTES compile time check Roy Pledge
2017-09-21 14:31 ` Catalin Marinas
2017-09-18 20:39 ` [v5 08/12] soc/fsl/qbman: Rework portal mapping calls for ARM/PPC Roy Pledge
[not found] ` <1505767187-4596-9-git-send-email-roy.pledge-3arQi8VN3Tc@public.gmane.org>
2017-09-21 14:32 ` Catalin Marinas
[not found] ` <1505767187-4596-1-git-send-email-roy.pledge-3arQi8VN3Tc@public.gmane.org>
2017-09-18 20:39 ` [v5 01/12] soc/fsl/qbman: Add common routine for QBMan private allocations Roy Pledge
[not found] ` <1505767187-4596-2-git-send-email-roy.pledge-3arQi8VN3Tc@public.gmane.org>
2017-09-21 14:29 ` Catalin Marinas
2017-09-18 20:39 ` [v5 02/12] soc/fsl/qbman: Use shared-dma-pool for BMan private memory allocations Roy Pledge
2017-09-21 14:30 ` Catalin Marinas
2017-09-18 20:39 ` [v5 07/12] soc/fsl/qbman: Fix ARM32 typo Roy Pledge
2017-09-21 14:32 ` Catalin Marinas
2017-09-18 20:39 ` [v5 09/12] soc/fsl/qbman: add QMAN_REV32 Roy Pledge
2017-09-18 20:39 ` [v5 10/12] soc/fsl/qbman: different register offsets on ARM Roy Pledge
2017-09-18 20:39 ` [v5 11/12] soc/fsl/qbman: Add missing headers " Roy Pledge
2017-09-18 20:39 ` [v5 12/12] soc/fsl/qbman: Enable FSL_LAYERSCAPE config " Roy Pledge
2017-09-21 14:40 ` [v5 00/12] soc/fsl/qbman: Enable QBMan on ARM Platforms Catalin Marinas
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=20170921143030.d6qafcrn4sy5bpap@localhost \
--to=catalin.marinas@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=mark.rutland@arm.com \
--cc=oss@buserror.net \
--cc=roy.pledge@nxp.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).