All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: myungjoo.ham@samsung.com, gregkh@linuxfoundation.org,
	kishon@ti.com, gg@slimlogic.co.uk,
	devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, grant.likely@linaro.org,
	rob.herring@calxeda.com
Subject: Re: [PATCH 1/2] extcon: palmas: rename device tree binding matching with file name
Date: Mon, 08 Jul 2013 10:34:29 +0900	[thread overview]
Message-ID: <51DA1725.3070403@samsung.com> (raw)
In-Reply-To: <1373032792-29001-1-git-send-email-ldewangan@nvidia.com>

On 07/05/2013 10:59 PM, Laxman Dewangan wrote:
> The driver name is extcon/extcon-palmas.c and hence renaming the
> device tree binding document to extcon-palmas.txt.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
>  .../extcon/{extcon-twl.txt => extcon-palmas.txt}   |    0
>  1 files changed, 0 insertions(+), 0 deletions(-)
>  rename Documentation/devicetree/bindings/extcon/{extcon-twl.txt => extcon-palmas.txt} (100%)
> 
> diff --git a/Documentation/devicetree/bindings/extcon/extcon-twl.txt b/Documentation/devicetree/bindings/extcon/extcon-palmas.txt
> similarity index 100%
> rename from Documentation/devicetree/bindings/extcon/extcon-twl.txt
> rename to Documentation/devicetree/bindings/extcon/extcon-palmas.txt
> 

Applied patch1 and patch2.

You can check it on following git repo:
- git.kernel.org/cgit/linux/kernel/git/chanwoo/extcon.git (extcon-linus)

Thanks,
Chanwoo Choi

      parent reply	other threads:[~2013-07-08  1:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 13:59 [PATCH 1/2] extcon: palmas: rename device tree binding matching with file name Laxman Dewangan
2013-07-05 13:59 ` Laxman Dewangan
2013-07-05 13:59 ` [PATCH 2/2] extcon: palmas: devicetree: remove non-require property details Laxman Dewangan
2013-07-05 13:59   ` Laxman Dewangan
2013-07-08  1:34 ` Chanwoo Choi [this message]

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=51DA1725.3070403@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gg@slimlogic.co.uk \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rob.herring@calxeda.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.