From: Laxman Dewangan <ldewangan@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH 2/2] input: gpio-keys: add support to name the gpio-keys
Date: Tue, 12 Jan 2016 20:54:08 +0530 [thread overview]
Message-ID: <56951A98.40502@nvidia.com> (raw)
In-Reply-To: <CAL_Jsq+ZLVNXVnQX+fYGjhqAx6aFrPNgBBXbPGTKrWoY52vMvw@mail.gmail.com>
On Tuesday 12 January 2016 08:53 PM, Rob Herring wrote:
> On Tue, Jan 12, 2016 at 8:55 AM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
>> On Tuesday 12 January 2016 08:13 PM, Rob Herring wrote:
>>> On Tue, Jan 12, 2016 at 05:02:50PM +0530, Laxman Dewangan wrote:
> So label is exactly for this purpose of defining user meaningful names.
>
Yes, I can use the label for name. I will update the patch.
Just for understanding, is "label" is better property name to pass the
specific name?
next prev parent reply other threads:[~2016-01-12 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:32 [PATCH 1/2] input: gpio-keys: add support for disable button from DT Laxman Dewangan
2016-01-12 11:32 ` [PATCH 2/2] input: gpio-keys: add support to name the gpio-keys Laxman Dewangan
2016-01-12 14:43 ` Rob Herring
2016-01-12 14:55 ` Laxman Dewangan
[not found] ` <569513E6.60608-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-01-12 15:23 ` Rob Herring
2016-01-12 15:24 ` Laxman Dewangan [this message]
2016-01-14 9:16 ` Linus Walleij
2016-01-12 21:19 ` [PATCH 1/2] input: gpio-keys: add support for disable button from DT Dmitry Torokhov
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=56951A98.40502@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).