From: Neil Armstrong <narmstrong@baylibre.com>
To: trini@konsulko.com
Cc: linux-amlogic@lists.infradead.org,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: [PULL u-boot] Please pull u-boot-amlogic-20190129
Date: Tue, 29 Jan 2019 11:22:15 +0100 [thread overview]
Message-ID: <65195f2f-1a96-babe-a08d-aa9f2899de33@baylibre.com> (raw)
Hi Tom,
Here is single patch adding support for pinconf on the amlogic pinctrl driver,
fixed after a build failure report from Anatolij.
This PR replaces u-boot-amlogic-20190128.
Thanks,
Neil
The following changes since commit 0da90255083681a02b24528f80da9d4062ff634a:
Merge branch '2019-01-25-master-imports' (2019-01-26 22:47:55 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-amlogic.git tags/u-boot-amlogic-20190129
for you to fetch changes up to c4c726c26bdc09a2c907e230fdf6c75adcc2b674:
pinctrl: meson: add pinconf support (2019-01-29 11:19:15 +0100)
----------------------------------------------------------------
Adds pinconf support for the Amlogic pinctrl driver (fixed)
----------------------------------------------------------------
Jerome Brunet (1):
pinctrl: meson: add pinconf support
drivers/pinctrl/meson/Kconfig | 1 +
drivers/pinctrl/meson/pinctrl-meson-axg-pmx.c | 10 +++
drivers/pinctrl/meson/pinctrl-meson-gx-pmx.c | 10 +++
drivers/pinctrl/meson/pinctrl-meson.c | 101 ++++++++++++++++++++++++--
drivers/pinctrl/meson/pinctrl-meson.h | 8 ++
5 files changed, 123 insertions(+), 7 deletions(-)
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-01-29 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 10:22 Neil Armstrong [this message]
2019-01-30 2:19 ` [PULL u-boot] Please pull u-boot-amlogic-20190129 Tom Rini
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=65195f2f-1a96-babe-a08d-aa9f2899de33@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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).