linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/19] mailbox: Device-managed registration
Date: Wed, 28 Nov 2018 10:39:50 +0100	[thread overview]
Message-ID: <20181128093950.GG17419@ulmo> (raw)
In-Reply-To: <20181121145429.7582-1-thierry.reding@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2933 bytes --]

On Wed, Nov 21, 2018 at 03:54:10PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Hi,
> 
> This series of patches adds device-managed registration functions for
> mailbox controllers. A number of drivers can be simplified by making use
> of this new API both in the error cleanup paths in their probe functions
> and in the driver remove implementation.
> 
> In addition to adding the new API this series converts all drivers to
> use it. There is also an additional cleanup patch for the mtk-cmdq
> driver that removes some calls to devm_kfree() that are not needed.
> 
> Thierry
> 
> Thierry Reding (19):
>   mailbox: Add device-managed registration functions
>   mailbox: arm-mhu: Use device-managed registration API
>   mailbox: bcm2835: Use device-managed registration API
>   mailbox: bcm-flexrm: Use device-managed registration API
>   mailbox: bcm-pdc: Use device-managed registration API
>   mailbox: hi3660: Use device-managed registration API
>   mailbox: hi6220: Use device-managed registration API
>   mailbox: imx: Use device-managed registration API
>   mailbox: altera: Use device-managed registration API
>   mailbox: sti: Use device-managed registration API
>   mailbox: xgene-slimpro: Use device-managed registration API
>   mailbox: mtk-cmdq: Use device-managed registration API
>   mailbox: mtk-cmdq: Remove needless devm_kfree() calls
>   mailbox: omap: Use device-managed registration API
>   mailbox: platform-mhu: Use device-managed registration API
>   mailbox: qcom-apcs: Use device-managed registration API
>   mailbox: rockchip: Use device-managed registration API
>   mailbox: stm32-ipcc: Use device-managed registration API
>   mailbox: ti-msgmgr: Use device-managed registration API
> 
>  drivers/mailbox/arm_mhu.c               | 12 +----
>  drivers/mailbox/bcm-flexrm-mailbox.c    |  4 +-
>  drivers/mailbox/bcm-pdc-mailbox.c       |  4 +-
>  drivers/mailbox/bcm2835-mailbox.c       | 10 +---
>  drivers/mailbox/hi3660-mailbox.c        | 11 +---
>  drivers/mailbox/hi6220-mailbox.c        | 11 +---
>  drivers/mailbox/imx-mailbox.c           |  3 +-
>  drivers/mailbox/mailbox-altera.c        | 15 +-----
>  drivers/mailbox/mailbox-sti.c           | 13 +----
>  drivers/mailbox/mailbox-xgene-slimpro.c | 11 +---
>  drivers/mailbox/mailbox.c               | 70 +++++++++++++++++++++++++
>  drivers/mailbox/mtk-cmdq-mailbox.c      | 11 +---
>  drivers/mailbox/omap-mailbox.c          |  4 +-
>  drivers/mailbox/platform_mhu.c          | 12 +----
>  drivers/mailbox/qcom-apcs-ipc-mailbox.c |  3 +-
>  drivers/mailbox/rockchip-mailbox.c      | 15 +-----
>  drivers/mailbox/stm32-ipcc.c            |  4 +-
>  drivers/mailbox/ti-msgmgr.c             | 13 +----
>  include/linux/mailbox_controller.h      |  5 ++
>  19 files changed, 92 insertions(+), 139 deletions(-)

Hi Jassi,

any comments on this?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-11-28  9:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 14:54 [PATCH 00/19] mailbox: Device-managed registration Thierry Reding
2018-11-21 14:54 ` [PATCH 01/19] mailbox: Add device-managed registration functions Thierry Reding
2018-11-21 14:54 ` [PATCH 02/19] mailbox: arm-mhu: Use device-managed registration API Thierry Reding
2018-11-21 14:54 ` [PATCH 03/19] mailbox: bcm2835: " Thierry Reding
2018-11-21 14:54 ` [PATCH 04/19] mailbox: bcm-flexrm: " Thierry Reding
2018-11-21 14:54 ` [PATCH 05/19] mailbox: bcm-pdc: " Thierry Reding
2018-11-21 14:54 ` [PATCH 06/19] mailbox: hi3660: " Thierry Reding
2018-11-21 14:54 ` [PATCH 07/19] mailbox: hi6220: " Thierry Reding
2018-11-21 14:54 ` [PATCH 08/19] mailbox: imx: " Thierry Reding
2018-11-21 14:54 ` [PATCH 09/19] mailbox: altera: " Thierry Reding
2018-11-21 14:54 ` [PATCH 10/19] mailbox: sti: " Thierry Reding
2018-11-21 14:54 ` [PATCH 11/19] mailbox: xgene-slimpro: " Thierry Reding
2018-11-21 14:54 ` [PATCH 12/19] mailbox: mtk-cmdq: " Thierry Reding
2018-11-21 14:54 ` [PATCH 13/19] mailbox: mtk-cmdq: Remove needless devm_kfree() calls Thierry Reding
2018-11-21 14:54 ` [PATCH 14/19] mailbox: omap: Use device-managed registration API Thierry Reding
2018-11-21 14:54 ` [PATCH 15/19] mailbox: platform-mhu: " Thierry Reding
2018-11-21 14:54 ` [PATCH 16/19] mailbox: qcom-apcs: " Thierry Reding
2018-11-21 14:54 ` [PATCH 17/19] mailbox: rockchip: " Thierry Reding
2018-11-21 14:54 ` [PATCH 18/19] mailbox: stm32-ipcc: " Thierry Reding
2018-11-21 14:54 ` [PATCH 19/19] mailbox: ti-msgmgr: " Thierry Reding
2018-11-28  9:39 ` Thierry Reding [this message]
2018-12-05 16:14   ` [PATCH 00/19] mailbox: Device-managed registration Thierry Reding
2018-12-07  4:09     ` Jassi Brar
2018-12-11 17:04 ` Jassi Brar
2018-12-17 14:35   ` Thierry Reding
2018-12-17 14:36     ` Jassi Brar

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=20181128093950.GG17419@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).