From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org
Cc: linux-samsung-soc@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL 4/5] ARM: samsung: mach for v5.4, second (replacing previous)
Date: Wed, 4 Sep 2019 19:50:01 +0200 [thread overview]
Message-ID: <20190904175002.10487-5-krzk@kernel.org> (raw)
In-Reply-To: <20190904175002.10487-1-krzk@kernel.org>
Hi,
Replaces previous pull (and it includes it).
Best regards,
Krzysztof
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-soc-5.4-2
for you to fetch changes up to c663d542bfb40eeeb6d393ed155c23a4666d65e1:
MAINTAINERS: Extend patterns for Samsung SoC, Security Subsystem and clock drivers (2019-08-22 21:04:45 +0200)
----------------------------------------------------------------
Samsung mach/soc changes for v5.4
1. Minor fixup in plat and mach code (S3C platforms),
2. Enable exynos-chipid driver to provide SoC related information,
3. Extend the patterns for Samsung maintainer entries to cover all
important files.
----------------------------------------------------------------
Krzysztof Kozlowski (1):
MAINTAINERS: Extend patterns for Samsung SoC, Security Subsystem and clock drivers
Linus Walleij (1):
ARM: samsung: Include GPIO driver header
Masahiro Yamada (1):
ARM: s3c64xx: squash samsung_usb_phy.h into setup-usb-phy.c
Pankaj Dubey (1):
ARM: exynos: Enable exynos-chipid driver
MAINTAINERS | 9 +++++++--
arch/arm/mach-exynos/Kconfig | 1 +
arch/arm/mach-s3c64xx/setup-usb-phy.c | 5 +++++
arch/arm/plat-samsung/include/plat/gpio-core.h | 1 +
arch/arm/plat-samsung/include/plat/usb-phy.h | 2 --
include/linux/usb/samsung_usb_phy.h | 17 -----------------
6 files changed, 14 insertions(+), 21 deletions(-)
delete mode 100644 include/linux/usb/samsung_usb_phy.h
_______________________________________________
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-09-04 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 17:49 [GIT PULL 0/5] arm: exynos: Second round of pulls for v5.4 Krzysztof Kozlowski
2019-09-04 17:49 ` [GIT PULL 1/5] ARM: defconfig: exynos " Krzysztof Kozlowski
2019-09-04 20:38 ` Arnd Bergmann
2019-09-04 17:49 ` [GIT PULL 2/5] soc: samsung: Second pull " Krzysztof Kozlowski
2019-09-04 20:38 ` Arnd Bergmann
2019-09-04 17:50 ` [GIT PULL 3/5] ARM: dts: exynos: " Krzysztof Kozlowski
2019-09-04 20:38 ` Arnd Bergmann
2019-09-04 17:50 ` Krzysztof Kozlowski [this message]
2019-09-04 20:39 ` [GIT PULL 4/5] ARM: samsung: mach for v5.4, second (replacing previous) Arnd Bergmann
2019-09-04 17:50 ` [PATCH 5/5] arm64: exynos: Enable exynos-chipid driver Krzysztof Kozlowski
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=20190904175002.10487-5-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.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;
as well as URLs for NNTP newsgroup(s).