All of lore.kernel.org
 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: Krzysztof Kozlowski <krzk@kernel.org>,
	Kukjin Kim <kgene@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL 2/5] soc: samsung: Second pull for v5.4
Date: Wed,  4 Sep 2019 19:49:59 +0200	[thread overview]
Message-ID: <20190904175002.10487-3-krzk@kernel.org> (raw)
In-Reply-To: <20190904175002.10487-1-krzk@kernel.org>

Hi,

On top of previous pull request.

Best regards,
Krzysztof


The following changes since commit 40d8aff614f71ab3cab20785b4f213e3802d4e87:

  soc: samsung: chipid: Convert exynos-chipid driver to use the regmap API (2019-08-15 20:25:25 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-drivers-5.4-2

for you to fetch changes up to 28578825ede61834a2c46e7f9a89012c4c7a667f:

  soc: samsung: chipid: Select missing dependency for EXYNOS_CHIPID (2019-08-22 20:16:20 +0200)

----------------------------------------------------------------
Samsung soc drivers changes for v5.4, part 2

Fixes and cleanups for recently introduced Exynos chipid driver.

----------------------------------------------------------------
Colin Ian King (1):
      soc: samsung: chipid: Fix memory leak in error path

Sylwester Nawrocki (2):
      soc: samsung: chipid: Remove the regmap lookup error log
      soc: samsung: chipid: Select missing dependency for EXYNOS_CHIPID

 drivers/soc/samsung/Kconfig         |  1 +
 drivers/soc/samsung/exynos-chipid.c | 18 +++++++++++-------
 2 files changed, 12 insertions(+), 7 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
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 2/5] soc: samsung: Second pull for v5.4
Date: Wed,  4 Sep 2019 19:49:59 +0200	[thread overview]
Message-ID: <20190904175002.10487-3-krzk@kernel.org> (raw)
In-Reply-To: <20190904175002.10487-1-krzk@kernel.org>

Hi,

On top of previous pull request.

Best regards,
Krzysztof


The following changes since commit 40d8aff614f71ab3cab20785b4f213e3802d4e87:

  soc: samsung: chipid: Convert exynos-chipid driver to use the regmap API (2019-08-15 20:25:25 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-drivers-5.4-2

for you to fetch changes up to 28578825ede61834a2c46e7f9a89012c4c7a667f:

  soc: samsung: chipid: Select missing dependency for EXYNOS_CHIPID (2019-08-22 20:16:20 +0200)

----------------------------------------------------------------
Samsung soc drivers changes for v5.4, part 2

Fixes and cleanups for recently introduced Exynos chipid driver.

----------------------------------------------------------------
Colin Ian King (1):
      soc: samsung: chipid: Fix memory leak in error path

Sylwester Nawrocki (2):
      soc: samsung: chipid: Remove the regmap lookup error log
      soc: samsung: chipid: Select missing dependency for EXYNOS_CHIPID

 drivers/soc/samsung/Kconfig         |  1 +
 drivers/soc/samsung/exynos-chipid.c | 18 +++++++++++-------
 2 files changed, 12 insertions(+), 7 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:[~2019-09-04 17:50 UTC|newest]

Thread overview: 24+ 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 ` Krzysztof Kozlowski
2019-09-04 17:49 ` [GIT PULL 1/5] ARM: defconfig: exynos " Krzysztof Kozlowski
2019-09-04 17:49   ` Krzysztof Kozlowski
2019-09-04 20:38   ` Arnd Bergmann
2019-09-04 20:38     ` Arnd Bergmann
2019-09-04 20:38     ` Arnd Bergmann
2019-09-04 17:49 ` Krzysztof Kozlowski [this message]
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 20:38     ` Arnd Bergmann
2019-09-04 20:38     ` Arnd Bergmann
2019-09-04 17:50 ` [GIT PULL 3/5] ARM: dts: exynos: " Krzysztof Kozlowski
2019-09-04 17:50   ` Krzysztof Kozlowski
2019-09-04 20:38   ` Arnd Bergmann
2019-09-04 20:38     ` Arnd Bergmann
2019-09-04 20:38     ` Arnd Bergmann
2019-09-04 17:50 ` [GIT PULL 4/5] ARM: samsung: mach for v5.4, second (replacing previous) Krzysztof Kozlowski
2019-09-04 17:50   ` Krzysztof Kozlowski
2019-09-04 20:39   ` Arnd Bergmann
2019-09-04 20:39     ` Arnd Bergmann
2019-09-04 20:39     ` Arnd Bergmann
2019-09-04 17:50 ` [PATCH 5/5] arm64: exynos: Enable exynos-chipid driver Krzysztof Kozlowski
2019-09-04 17:50   ` 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-3-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 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.