From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes
Date: Tue, 30 May 2017 15:07:56 -0700 [thread overview]
Message-ID: <m2fufmt2v7.fsf@baylibre.com> (raw)
In-Reply-To: <1495549311-23660-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Tue, 23 May 2017 16:21:48 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> This patchset fixes the following :
> - bad gpio-ranges for GXL
> - bad pull-enable register base for GXBB & GXL
Applied with Jerome's reviewed-by tag added.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes
Date: Tue, 30 May 2017 15:07:56 -0700 [thread overview]
Message-ID: <m2fufmt2v7.fsf@baylibre.com> (raw)
In-Reply-To: <1495549311-23660-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Tue, 23 May 2017 16:21:48 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> This patchset fixes the following :
> - bad gpio-ranges for GXL
> - bad pull-enable register base for GXBB & GXL
Applied with Jerome's reviewed-by tag added.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes
Date: Tue, 30 May 2017 15:07:56 -0700 [thread overview]
Message-ID: <m2fufmt2v7.fsf@baylibre.com> (raw)
In-Reply-To: <1495549311-23660-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Tue, 23 May 2017 16:21:48 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> This patchset fixes the following :
> - bad gpio-ranges for GXL
> - bad pull-enable register base for GXBB & GXL
Applied with Jerome's reviewed-by tag added.
Kevin
next prev parent reply other threads:[~2017-05-30 22:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:21 [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` [PATCH 1/3] ARM64: dts: meson-gxl: Fix pinctrl periphs gpio-ranges Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-24 8:39 ` Jerome Brunet
2017-05-24 8:39 ` Jerome Brunet
2017-05-24 8:39 ` Jerome Brunet
2017-05-24 8:39 ` Jerome Brunet
2017-05-23 14:21 ` [PATCH 2/3] ARM64: dts: Fix GXL periphs pinctrl pull-enable register base Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-24 8:39 ` Jerome Brunet
2017-05-24 8:39 ` Jerome Brunet
2017-05-24 8:39 ` Jerome Brunet
2017-05-23 14:21 ` [PATCH 3/3] ARM64: dts: Fix GXBB " Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-23 14:21 ` Neil Armstrong
2017-05-24 8:40 ` Jerome Brunet
2017-05-24 8:40 ` Jerome Brunet
2017-05-24 8:40 ` Jerome Brunet
2017-05-24 8:40 ` Jerome Brunet
2017-05-30 22:07 ` Kevin Hilman [this message]
2017-05-30 22:07 ` [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes Kevin Hilman
2017-05-30 22:07 ` Kevin Hilman
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=m2fufmt2v7.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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.