From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC Date: Wed, 9 Mar 2016 18:04:26 +0700 Message-ID: References: <1457005303-26829-1-git-send-email-yendapally.reddy@broadcom.com> <1457005303-26829-3-git-send-email-yendapally.reddy@broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-oi0-f54.google.com ([209.85.218.54]:36025 "EHLO mail-oi0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753133AbcCILE1 (ORCPT ); Wed, 9 Mar 2016 06:04:27 -0500 Received: by mail-oi0-f54.google.com with SMTP id r187so32422988oih.3 for ; Wed, 09 Mar 2016 03:04:26 -0800 (PST) In-Reply-To: <1457005303-26829-3-git-send-email-yendapally.reddy@broadcom.com> Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: Yendapally Reddy Dhananjaya Reddy , Ray Jui , Stefan Wahren , Stephen Warren , Florian Fainelli , Pramod KUMAR , Jonathan Bell Cc: Scott Branden , "linux-kernel@vger.kernel.org" , bcm-kernel-feedback-list , "linux-arm-kernel@lists.infradead.org" , "linux-gpio@vger.kernel.org" On Thu, Mar 3, 2016 at 6:41 PM, Yendapally Reddy Dhananjaya Reddy wrote: > This adds the initial support of the Broadcom NS2 pinmux driver > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753405AbcCILEg (ORCPT ); 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 ); 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: Subject: Re: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC From: Linus Walleij To: Yendapally Reddy Dhananjaya Reddy , Ray Jui , Stefan Wahren , Stephen Warren , Florian Fainelli , Pramod KUMAR , Jonathan Bell Cc: Scott Branden , "linux-kernel@vger.kernel.org" , bcm-kernel-feedback-list , "linux-arm-kernel@lists.infradead.org" , "linux-gpio@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 3, 2016 at 6:41 PM, Yendapally Reddy Dhananjaya Reddy wrote: > This adds the initial support of the Broadcom NS2 pinmux driver > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: linus.walleij@linaro.org (Linus Walleij) Date: Wed, 9 Mar 2016 18:04:26 +0700 Subject: [PATCH 2/3] pinctrl: ns2: add pinmux driver support for Broadcom NS2 SoC 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> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Mar 3, 2016 at 6:41 PM, Yendapally Reddy Dhananjaya Reddy wrote: > This adds the initial support of the Broadcom NS2 pinmux driver > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy 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