From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>,
Rob Herring <rob.herring@calxeda.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Stephen Warren <swarren@nvidia.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>
Subject: Re: [PATCH 1/2] include: dt-binding: input: create a DT header defining key codes.
Date: Mon, 19 Aug 2013 10:24:56 -0600 [thread overview]
Message-ID: <521246D8.9040506@wwwdotorg.org> (raw)
In-Reply-To: <52123152.9070408@nvidia.com>
On 08/19/2013 08:53 AM, Laxman Dewangan wrote:
> On Monday 12 August 2013 11:29 PM, Stephen Warren wrote:
>> On 08/12/2013 11:15 AM, Dmitry Torokhov wrote:
>>>>
>>>> Device tree files can only include headers in include/dt-bindings.
>>>> Eventually/soon, all the DT files and the headers in the dt-bindings/
>>>> directory will be split out into a separate git tree, which does not
>>>> have access to include/uapi, or indeed any other Linux kernel header
>>>> files.
>>> OK, that makes it easier for me - please merge through whatever tree
>>> that owns include/dt-bindings.
>> Are there any objections to my taking both patches through the Tegra
>> tree? Patch 2/2 depends on 1/2 and is Tegra-specific. This should work
>> out fine unless anyone else wants to use the new header this kernel
>> cycle; if they do, this should go into a topic branch in the DT tree
>> that I can pull into the Tegra tree.
>
> Hi Stephen,
> Just wanted to check if you are taking this on Tegra tree. I want to
> post some more cleanups on other dts file to use dt-binding include for
> key code otherwise I will defer for next kernel version.
At this time, I assume this will go through the DT repo/branch. Rob?
next prev parent reply other threads:[~2013-08-19 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 14:12 [PATCH 1/2] include: dt-binding: input: create a DT header defining key codes Laxman Dewangan
2013-08-06 14:12 ` [PATCH 2/2] ARM: tegra: use dt-binding header for key code Laxman Dewangan
2013-08-06 19:28 ` Stephen Warren
2013-08-06 14:28 ` [PATCH 1/2] include: dt-binding: input: create a DT header defining key codes Jason Cooper
2013-08-06 19:28 ` Stephen Warren
2013-08-08 17:11 ` Laxman Dewangan
2013-08-08 17:13 ` Dmitry Torokhov
2013-08-08 17:25 ` Stephen Warren
2013-08-12 17:15 ` Dmitry Torokhov
2013-08-12 17:59 ` Stephen Warren
2013-08-19 14:53 ` Laxman Dewangan
2013-08-19 16:24 ` Stephen Warren [this message]
2013-08-19 22:35 ` Rob Herring
2013-08-08 17:32 ` Laxman Dewangan
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=521246D8.9040506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Mark.Rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox