Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753405AbcCILEg (ORCPT <rfc822;w@1wt.eu>);
	Wed, 9 Mar 2016 06:04:36 -0500
Received: from mail-oi0-f46.google.com ([209.85.218.46]:33770 "EHLO
	mail-oi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753329AbcCILE1 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 9 Mar 2016 06:04:27 -0500
MIME-Version: 1.0
In-Reply-To: <1457005303-26829-3-git-send-email-yendapally.reddy@broadcom.com>
References: <1457005303-26829-1-git-send-email-yendapally.reddy@broadcom.com>
	<1457005303-26829-3-git-send-email-yendapally.reddy@broadcom.com>
Date: Wed, 9 Mar 2016 18:04:26 +0700
Message-ID: <CACRpkdaKn4puDsZBPSbfkmHW4KHqBW8q1T2vpyNk_0Yb7C0AXQ@mail.gmail.com>
Subject: Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom
 NS2 SoC
From: Linus Walleij <linus.walleij@linaro.org>
To: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>,
        Ray Jui <rjui@broadcom.com>, Stefan Wahren <stefan.wahren@i2se.com>,
        Stephen Warren <swarren@wwwdotorg.org>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Pramod KUMAR <pramodku@broadcom.com>,
        Jonathan Bell <jonathan@raspberrypi.org>
Cc: Scott Branden <sbranden@broadcom.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
        "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
        "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 555
Lines: 22

On Thu, Mar 3, 2016 at 6:41 PM, Yendapally Reddy Dhananjaya Reddy
<yendapally.reddy@broadcom.com> wrote:

> This adds the initial support of the Broadcom NS2 pinmux driver
>
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>

Now yet another Broadcom driver!

Can I get the help of the maintainers of the other
Broadcom drivers to say:

- If this looks sane

- If this hardware looks suspiciously similar to one of the
  other drivers and should rather me a subdriver of one of
  the existing ones

?

Yours,
Linus Walleij