From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Dinh Nguyen <dinguyen@kernel.org>
Subject: Re: [PATCH] ARM: dts: socfpga: Fix up button mapping on VINING FPGA
Date: Wed, 7 Aug 2019 13:13:07 +0200 [thread overview]
Message-ID: <a7c317e9-22d2-965e-7143-b07014cb5dfe@denx.de> (raw)
In-Reply-To: <20190628001920.1416-1-marex@denx.de>
On 6/28/19 2:19 AM, Marek Vasut wrote:
> Add missing buttons and signals to the VINING FPGA device tree,
> so they are presented to the userspace via gpio-keys evdev.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Dinh Nguyen <dinguyen@kernel.org>
Bump ?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-07 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 0:19 [PATCH] ARM: dts: socfpga: Fix up button mapping on VINING FPGA Marek Vasut
2019-07-01 14:59 ` Dinh Nguyen
2019-08-07 11:13 ` Marek Vasut [this message]
2019-08-07 14:10 ` Dinh Nguyen
2019-08-08 9:39 ` Marek Vasut
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=a7c317e9-22d2-965e-7143-b07014cb5dfe@denx.de \
--to=marex@denx.de \
--cc=dinguyen@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