Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751933AbdIUOkd (ORCPT ); Thu, 21 Sep 2017 10:40:33 -0400 Received: from foss.arm.com ([217.140.101.70]:47772 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751734AbdIUOkc (ORCPT ); Thu, 21 Sep 2017 10:40:32 -0400 Date: Thu, 21 Sep 2017 15:40:28 +0100 From: Catalin Marinas To: Roy Pledge 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 00/12] soc/fsl/qbman: Enable QBMan on ARM Platforms Message-ID: <20170921144028.nv2f54w55quyabje@localhost> References: <1505767187-4596-1-git-send-email-roy.pledge@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1505767187-4596-1-git-send-email-roy.pledge@nxp.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1065 Lines: 27 On Mon, Sep 18, 2017 at 04:39:35PM -0400, Roy Pledge wrote: > Madalin Bucur (4): > soc/fsl/qbman: Drop set/clear_bits usage > soc/fsl/qbman: add QMAN_REV32 > soc/fsl/qbman: different register offsets on ARM > soc/fsl/qbman: Enable FSL_LAYERSCAPE config on ARM > > Roy Pledge (5): > soc/fsl/qbman: Add common routine for QBMan private allocations > soc/fsl/qbman: Use shared-dma-pool for BMan private memory allocations > soc/fsl/qbman: Use shared-dma-pool for QMan private memory allocations > dt-bindings: soc/fsl: Update reserved memory binding for QBMan > soc/fsl/qbman: Rework portal mapping calls for ARM/PPC > > Valentin Rothberg (1): > soc/fsl/qbman: Fix ARM32 typo I reviewed the patches specific to the arm qbman buffer mappings, they look fine to me. The DT bindings would need acks from the devicetree maintainers. The rest of the patches are qbman-specific definitions which I haven't checked for correctness (I guess they are fine). How do you plan to upstream these patches? They would probably go in via arm-soc. -- Catalin