linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Input: tegra-kbc - add device tree support
Date: Tue, 03 Jan 2012 15:21:35 -0800	[thread overview]
Message-ID: <2662846.nxkJH3EzFi@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <CAOesGMhYscMgsNbZ+W0vdcRFmMiV3yQYLRxgGLfMVHKuhEAe-w@mail.gmail.com>

On Tuesday, January 03, 2012 02:58:57 PM Olof Johansson wrote:
> On Tue, Jan 3, 2012 at 2:42 PM, Stephen Warren <swarren@nvidia.com> wrote:
> > Olof Johansson wrote at Tuesday, January 03, 2012 3:28 PM:
> >> This includes an optional "linux,fn-keymap" binding that is not yet
> >> implemented, that will be used to specify the Fn-key modifier layout
> >> if needed.
> >> 
> >> diff --git a/Documentation/devicetree/bindings/input/tegra-kbc.txt
> > 
> > ...
> > 
> >> +Required properties:
> >> +- compatible: "nvidia,tegra20-kbc", "matrix-keyboard-controller"
> > 
> > I think "matrix-keyboard-controller" should be dropped now?
> 
> Crap, yeah, I had dropped it but forgot to commit before I did send-email.
> 
> Dmitry, if this is the only comment, do you want me to resend or are
> you OK with editing yourself before applying?

Olof,

Any chance I could get a patch against my 'next' branch? I already applied
patch that did DT bindings without keymap support.

Thanks.

-- 
Dmitry

      reply	other threads:[~2012-01-03 23:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 22:52 [PATCH] Input: keyboard - add device tree bindings for simple key matrixes Olof Johansson
2011-12-28 23:30 ` Rob Herring
2011-12-28 23:37   ` Olof Johansson
2011-12-29  6:16 ` Stephen Warren
2011-12-29  6:34   ` Olof Johansson
2011-12-29  7:01     ` Stephen Warren
2011-12-29  7:06       ` Olof Johansson
2011-12-29 19:28         ` Rob Herring
2012-01-02  4:11         ` Thomas Abraham
2012-01-02  7:21         ` Grant Likely
2012-01-03 17:44           ` Olof Johansson
2011-12-29 18:42 ` [PATCH v2] " Olof Johansson
2011-12-29 21:14   ` Rob Herring
2011-12-29 21:33     ` Olof Johansson
2011-12-29 22:05   ` Dmitry Torokhov
2011-12-29 22:26     ` Olof Johansson
2012-01-02  6:09   ` [PATCH v3] " Olof Johansson
2012-01-02 18:39     ` Simon Glass
2012-01-03 15:43       ` Olof Johansson
2012-01-03 16:22         ` Simon Glass
2012-01-03 16:29           ` Russell King - ARM Linux
2012-01-03 16:44             ` Dmitry Torokhov
2012-01-03 16:48               ` Olof Johansson
2012-01-03 17:06               ` Russell King - ARM Linux
2012-01-03 17:57                 ` Dmitry Torokhov
2012-01-03 17:46     ` Stephen Warren
2012-01-03 21:37     ` [PATCH v4] " Olof Johansson
2012-01-03 22:37       ` Stephen Warren
2012-01-08  1:05         ` Simon Glass
2012-03-14  4:42         ` Dmitry Torokhov
2012-01-03 22:28     ` [PATCH] Input: tegra-kbc - add device tree support Olof Johansson
2012-01-03 22:42       ` Stephen Warren
2012-01-03 22:58         ` Olof Johansson
2012-01-03 23:21           ` Dmitry Torokhov [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=2662846.nxkJH3EzFi@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).