linux-kernel - Re: [PATCHv6 2/3] mailbox: Introduce framework for mailbox

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140605105127.GB32082@beef>
Date:	Thu, 5 Jun 2014 06:51:27 -0400
From:	Matt Porter <mporter@...aro.org>
To:	Jassi Brar <jaswinder.singh@...aro.org>
Cc:	linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
	s-anna@...com, loic.pallardy@...com, lftan.linux@...il.com,
	slapdau@...oo.com.au, courtney.cavin@...ymobile.com,
	robherring2@...il.com, arnd@...db.de, joshc@...eaurora.org,
	linus.walleij@...aro.org, galak@...eaurora.org,
	ks.giri@...sung.com, patches@...aro.org, bjorn@...o.se
Subject: Re: [PATCHv6 2/3] mailbox: Introduce framework for mailbox

On Tue, Jun 03, 2014 at 12:01:24AM +0530, Jassi Brar wrote:
> Introduce common framework for client/protocol drivers and
> controller drivers of Inter-Processor-Communication (IPC).
> 
> Client driver developers should have a look at
>  include/linux/mailbox_client.h to understand the part of
> the API exposed to client drivers.
> Similarly controller driver developers should have a look
> at include/linux/mailbox_controller.h
> 
> Signed-off-by: Jassi Brar <jaswinder.singh@...aro.org>
> ---
>  .../devicetree/bindings/mailbox/mailbox.txt        |  33 ++
>  drivers/mailbox/Makefile                           |   4 +
>  drivers/mailbox/mailbox.c                          | 487 +++++++++++++++++++++
>  include/linux/mailbox_client.h                     |  45 ++
>  include/linux/mailbox_controller.h                 | 121 +++++

Could you please include all the DT maintainers here? It's a generic
binding that needs wider review and an ack. The binding should be
separated as noted below.

>From Documentations/devicetree/bindings/submitting-patches.txt:

I. For patch submitters

  0) Normal patch submission rules from Documentation/SubmittingPatches
     applies.

  1) The Documentation/ portion of the patch should be a separate patch.

  2) Submit the entire series to the devicetree mailinglist at

       devicetree@...r.kernel.org

-Matt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/