lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 29 Mar 2017 11:22:25 +0530 From: Anup Patel <anup.patel@...adcom.com> To: Jassi Brar <jassisinghbrar@...il.com> Cc: Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Ray Jui <rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>, Pramod KUMAR <pramod.kumar@...adcom.com>, Rob Rice <rob.rice@...adcom.com>, Devicetree List <devicetree@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com> Subject: Re: [PATCH v7 0/3] Broadcom FlexRM ring manager support On Wed, Mar 29, 2017 at 11:05 AM, Jassi Brar <jassisinghbrar@...il.com> wrote: > On Wed, Mar 29, 2017 at 11:00 AM, Anup Patel <anup.patel@...adcom.com> wrote: >> The Broadcom FlexRM ring manager provides producer-consumer style >> ring interface for offload engines on Broadcom iProc SoCs. We can >> have one or more instances of Broadcom FlexRM ring manager in a SoC. >> >> This patchset adds a mailbox driver for Broadcom FlexRM ring manager >> which can be used by offload engine drivers as mailbox clients. >> >> The Broadcom FlexRM mailbox driver is feature complete for RAID and >> Crypto offload engines. We will have incremental patches in-future >> for ring-level statistics using debugfs and minor optimizations. >> >> This patchset is based on Linux-4.11-rc4 and it is also available >> at flexrm-v7 branch of https://github.com/Broadcom/arm64-linux.git >> >> Changes since v6: >> - Rebased patches for Linux-4.11-rc4 >> - Added a patch to remove depends on COMPILE_TEST for kconfig >> option BCM_FLEXRM_MBOX >> > You only needed to send the fix to compilation failure reports, not > the whole series. My bad for the noise. > I believe only the patch-3 is new in the series and I need not even > look at patch-1,2 ? Yes, only patch-3 is required to fix compilation failure. Regards, Anup
Powered by blists - more mailing lists