From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx50: fix KPP pin definition typos
Date: Sun, 1 Jul 2018 17:06:13 +0800 [thread overview]
Message-ID: <20180701090612.GL4348@dragon> (raw)
In-Reply-To: <20180624055929.10011-1-akurz@blala.de>
On Sun, Jun 24, 2018 at 05:59:29AM +0000, Alexander Kurz wrote:
> iMX50 pin mux options for pads KEY_COL2 and KEY_COL3 allow muxing the same
> KEY_COL instances as the pad name. Fix typos shifting KEY_COL instances.
>
> Signed-off-by: Alexander Kurz <akurz@blala.de>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Alexander Kurz <akurz@blala.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] ARM: dts: imx50: fix KPP pin definition typos
Date: Sun, 1 Jul 2018 17:06:13 +0800 [thread overview]
Message-ID: <20180701090612.GL4348@dragon> (raw)
In-Reply-To: <20180624055929.10011-1-akurz@blala.de>
On Sun, Jun 24, 2018 at 05:59:29AM +0000, Alexander Kurz wrote:
> iMX50 pin mux options for pads KEY_COL2 and KEY_COL3 allow muxing the same
> KEY_COL instances as the pad name. Fix typos shifting KEY_COL instances.
>
> Signed-off-by: Alexander Kurz <akurz@blala.de>
Applied, thanks.
next prev parent reply other threads:[~2018-07-01 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 5:59 [PATCH] ARM: dts: imx50: fix KPP pin definition typos Alexander Kurz
2018-06-24 5:59 ` Alexander Kurz
2018-07-01 9:06 ` Shawn Guo [this message]
2018-07-01 9:06 ` Shawn Guo
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=20180701090612.GL4348@dragon \
--to=shawnguo@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 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.