linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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,
	linux-arm-kernel@lists.infradead.org,
	Krzysztof Kozlowski <krzk@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL 3/3] arm64: dts: samsung: DTS for v5.12
Date: Mon, 25 Jan 2021 20:12:40 +0100	[thread overview]
Message-ID: <20210125191240.11278-4-krzk@kernel.org> (raw)
In-Reply-To: <20210125191240.11278-1-krzk@kernel.org>

The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:

  Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt64-5.12

for you to fetch changes up to 545a540a9c2ec192cdd5c75af1e334711a79354a:

  arm64: dts: exynos: correct S3FWRN5 NFC interrupt trigger level on TM2 (2020-12-29 16:47:20 +0100)

----------------------------------------------------------------
Samsung DTS ARM64 changes for v5.12

Correct Samsung PMIC and S3FWRN5 NFC interrupts trigger levels on
TM2/TM2E and Espresso boards.

----------------------------------------------------------------
Krzysztof Kozlowski (3):
      arm64: dts: exynos: correct PMIC interrupt trigger level on TM2
      arm64: dts: exynos: correct PMIC interrupt trigger level on Espresso
      arm64: dts: exynos: correct S3FWRN5 NFC interrupt trigger level on TM2

 arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 4 ++--
 arch/arm64/boot/dts/exynos/exynos7-espresso.dts       | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-01-25 19:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 19:12 [GIT PULL 0/3] Samsung for v5.12 Krzysztof Kozlowski
2021-01-25 19:12 ` [GIT PULL 1/3] soc: samsung: drivers " Krzysztof Kozlowski
2021-01-30 11:28   ` Arnd Bergmann
2021-01-25 19:12 ` [GIT PULL 2/3] ARM: dts: samsung: DTS " Krzysztof Kozlowski
2021-02-06 13:45   ` Krzysztof Kozlowski
2021-02-06 14:35     ` Arnd Bergmann
2021-02-06 15:06       ` Krzysztof Kozlowski
2021-02-06 19:47       ` Geert Uytterhoeven
2021-02-08  8:40         ` Tony Lindgren
2021-02-08 18:21         ` Bjorn Andersson
2021-02-08 18:42           ` Krzysztof Kozlowski
2021-02-08 19:52             ` Arnd Bergmann
2021-02-08 21:35               ` Alexandre Belloni
2021-02-08 22:14                 ` Arnd Bergmann
2021-02-08 23:10                   ` Alexandre Belloni
2021-02-09  8:25                     ` Geert Uytterhoeven
2021-02-09 14:27                     ` Rob Herring
2021-02-09 17:11                       ` Bjorn Andersson
2021-02-09 19:19       ` Frank Rowand
2021-02-09 23:06   ` Arnd Bergmann
2021-01-25 19:12 ` Krzysztof Kozlowski [this message]
2021-01-30 11:34   ` [GIT PULL 3/3] arm64: " Arnd Bergmann

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=20210125191240.11278-4-krzk@kernel.org \
    --to=krzk@kernel.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --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).