public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/7] Documentation: Rename gpio controller name from cygnus to iproc
Date: Fri, 20 Nov 2015 09:34:37 -0600	[thread overview]
Message-ID: <20151120153437.GA7645@rob-hp-laptop> (raw)
In-Reply-To: <1447905139-16002-7-git-send-email-pramodku@broadcom.com>

On Thu, Nov 19, 2015 at 09:22:18AM +0530, Pramod Kumar wrote:
> Renamed gpio controller's driver name from cygnus to iproc to make it
> more generic so that all iProc based SoCs having the same gpio controller
> could use this.
> 
> Signed-off-by: Pramod Kumar <pramodku@broadcom.com>
> Reviewed-by: Ray Jui <rjui@broadcom.com>
> Reviewed-by: Scott Branden <sbranden@broadcom.com>

Where's my ack?

> ---
>  .../bindings/pinctrl/{brcm,cygnus-gpio.txt => brcm,iproc-gpio.txt}    | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename Documentation/devicetree/bindings/pinctrl/{brcm,cygnus-gpio.txt => brcm,iproc-gpio.txt} (97%)
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> similarity index 97%
> rename from Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt
> rename to Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> index 8b1e5d1..e427792 100644
> --- a/Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,iproc-gpio.txt
> @@ -1,4 +1,4 @@
> -Broadcom Cygnus GPIO/PINCONF Controller
> +Broadcom iProc GPIO/PINCONF Controller
>  
>  Required properties:
>  
> @@ -7,7 +7,7 @@ Required properties:
>      "brcm,cygnus-crmu-gpio" or "brcm,iproc-gpio"
>  
>  - reg:
> -    Define the base and range of the I/O address space that contains the Cygnus
> +    Define the base and range of the I/O address space that contains SoC
>  GPIO/PINCONF controller registers
>  
>  - ngpios:
> -- 
> 1.9.1
> 

  reply	other threads:[~2015-11-20 15:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  3:52 [PATCH v2 0/7] Generalized broadcom cygnus gpio driver Pramod Kumar
2015-11-19  3:52 ` [PATCH v2 1/7] dt-binding: Add ngpios property to GPIO controller node Pramod Kumar
2015-11-20 15:33   ` Rob Herring
2015-11-30  8:34   ` Linus Walleij
2015-11-19  3:52 ` [PATCH v2 2/7] dts: define ngpios property in gpio controller's node Pramod Kumar
2015-11-25  0:11   ` Florian Fainelli
2015-11-30  8:35   ` Linus Walleij
2015-11-19  3:52 ` [PATCH v2 3/7] pinctrl: use ngpios propety from DT Pramod Kumar
2015-11-30  8:36   ` Linus Walleij
2015-11-19  3:52 ` [PATCH v2 4/7] pinctrl: Add new compatible string to GPIO controller driver Pramod Kumar
2015-11-30  8:37   ` Linus Walleij
2015-11-19  3:52 ` [PATCH v2 5/7] gpio: Rename func/macro/var to IP-block,iproc Pramod Kumar
2015-11-30  8:41   ` Linus Walleij
2015-11-19  3:52 ` [PATCH v2 6/7] Documentation: Rename gpio controller name from cygnus to iproc Pramod Kumar
2015-11-20 15:34   ` Rob Herring [this message]
2015-11-20 17:03     ` Pramod Kumar
2015-11-30  8:43   ` Linus Walleij
2015-11-19  3:52 ` [PATCH v2 7/7] pinctrl: Rename gpio driver " Pramod Kumar
2015-11-30  8:44   ` Linus Walleij

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=20151120153437.GA7645@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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