Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1611588 > unrolled thread
| Started by | Jassi Brar <jassisinghbrar@gmail.com> |
|---|---|
| First post | 2017-03-29 07:40 +0200 |
| Last post | 2017-03-29 08:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v7 0/3] Broadcom FlexRM ring manager support Jassi Brar <jassisinghbrar@gmail.com> - 2017-03-29 07:40 +0200
Re: [PATCH v7 0/3] Broadcom FlexRM ring manager support Anup Patel <anup.patel@broadcom.com> - 2017-03-29 08:00 +0200
| From | Jassi Brar <jassisinghbrar@gmail.com> |
|---|---|
| Date | 2017-03-29 07:40 +0200 |
| Subject | Re: [PATCH v7 0/3] Broadcom FlexRM ring manager support |
| Message-ID | <tqeuS-2mb-25@gated-at.bofh.it> |
On Wed, Mar 29, 2017 at 11:00 AM, Anup Patel <anup.patel@broadcom.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. I believe only the patch-3 is new in the series and I need not even look at patch-1,2 ?
[toc] | [next] | [standalone]
| From | Anup Patel <anup.patel@broadcom.com> |
|---|---|
| Date | 2017-03-29 08:00 +0200 |
| Message-ID | <tqeOd-2vj-3@gated-at.bofh.it> |
| In reply to | #1611588 |
On Wed, Mar 29, 2017 at 11:05 AM, Jassi Brar <jassisinghbrar@gmail.com> wrote: > On Wed, Mar 29, 2017 at 11:00 AM, Anup Patel <anup.patel@broadcom.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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web