From: Lee Jones <lee.jones@linaro.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Mallikarjun Kasoju <mkasoju@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Immutable branch between MFD and Regulator due for the v5.2 merge window
Date: Wed, 8 May 2019 12:51:37 +0100 [thread overview]
Message-ID: <20190508115137.GM31645@dell> (raw)
In-Reply-To: <20190505154325.30026-1-digetx@gmail.com>
Enjoy!
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-regulator-v5.2
for you to fetch changes up to 744b13107d0d2ec36c5293d7b59129d3186c9396:
mfd: max77620: Provide system power-off functionality (2019-05-08 12:50:14 +0100)
----------------------------------------------------------------
Immutable branch between MFD and Regulator due for the v5.2 merge window
----------------------------------------------------------------
Dmitry Osipenko (5):
dt-bindings: mfd: max77620: Add compatible for Maxim 77663
dt-bindings: mfd: max77620: Add system-power-controller property
mfd: max77620: Fix swapped FPS_PERIOD_MAX_US values
mfd: max77620: Support Maxim 77663
mfd: max77620: Provide system power-off functionality
Documentation/devicetree/bindings/mfd/max77620.txt | 9 ++-
drivers/mfd/max77620.c | 87 +++++++++++++++++++++-
include/linux/mfd/max77620.h | 5 +-
3 files changed, 97 insertions(+), 4 deletions(-)
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-05-08 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 15:43 [PATCH v4 0/6] Add support for Maxim 77663 MFD Dmitry Osipenko
2019-05-05 15:43 ` [PATCH v4 1/6] dt-bindings: mfd: max77620: Add compatible for Maxim 77663 Dmitry Osipenko
2019-05-08 11:46 ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 2/6] dt-bindings: mfd: max77620: Add system-power-controller property Dmitry Osipenko
2019-05-07 17:46 ` Rob Herring
2019-05-08 11:46 ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 3/6] mfd: max77620: Fix swapped FPS_PERIOD_MAX_US values Dmitry Osipenko
2019-05-08 11:47 ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 4/6] mfd: max77620: Support Maxim 77663 Dmitry Osipenko
2019-05-08 11:47 ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 5/6] mfd: max77620: Provide system power-off functionality Dmitry Osipenko
2019-05-08 11:48 ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 6/6] regulator: max77620: Support Maxim 77663 Dmitry Osipenko
2019-05-12 14:08 ` Dmitry Osipenko
2019-05-12 17:07 ` Mark Brown
2019-05-08 11:51 ` Lee Jones [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=20190508115137.GM31645@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkasoju@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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.