From: Anup Patel <anup.patel@broadcom.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
Anup Patel <anup.patel@broadcom.com>
Subject: [PATCH 0/5] Few more FlexRM driver improvements
Date: Tue, 3 Oct 2017 10:51:47 +0530 [thread overview]
Message-ID: <1507008112-27117-1-git-send-email-anup.patel@broadcom.com> (raw)
This patchset does few more improvements to Broadcom FlexRM mailbox
driver.
The patches are based on Linux-4.14-rc3 and can also be found at
flexrm-imp2-v1 branch of:
https://github.com/Broadcom/arm64-linux.git
Anup Patel (4):
mailbox: bcm-flexrm-mailbox: Fix FlexRM ring flush sequence
mailbox: bcm-flexrm-mailbox: Print ring number in errors and warnings
mailbox: bcm-flexrm-mailbox: Use common GPL comment header
mailbox: Build Broadcom FlexRM driver as loadable module for iProc
SOCs
Scott Branden (1):
mailbox: bcm-flexrm-mailbox: add depends on ARCH_BCM_IPROC
drivers/mailbox/Kconfig | 3 +-
drivers/mailbox/bcm-flexrm-mailbox.c | 66 ++++++++++++++++++++++++++----------
2 files changed, 51 insertions(+), 18 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-03 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 5:21 Anup Patel [this message]
2017-10-03 5:21 ` [PATCH 1/5] mailbox: bcm-flexrm-mailbox: Fix FlexRM ring flush sequence Anup Patel
2017-10-03 5:21 ` [PATCH 2/5] mailbox: bcm-flexrm-mailbox: Print ring number in errors and warnings Anup Patel
2017-10-03 5:21 ` [PATCH 3/5] mailbox: bcm-flexrm-mailbox: add depends on ARCH_BCM_IPROC Anup Patel
2017-10-03 5:21 ` [PATCH 4/5] mailbox: bcm-flexrm-mailbox: Use common GPL comment header Anup Patel
2017-10-03 5:21 ` [PATCH 5/5] mailbox: Build Broadcom FlexRM driver as loadable module for iProc SOCs Anup Patel
2017-10-27 5:20 ` [PATCH 0/5] Few more FlexRM driver improvements Anup Patel
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=1507008112-27117-1-git-send-email-anup.patel@broadcom.com \
--to=anup.patel@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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
all inboxes | Powered by JetHome®