linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL 5/9] ARM: tegra: Core changes for v5.2-rc1
Date: Thu, 18 Apr 2019 17:07:16 +0200	[thread overview]
Message-ID: <20190418150721.8828-5-thierry.reding@gmail.com> (raw)
In-Reply-To: <20190418150721.8828-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:

  Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.2-arm-soc

for you to fetch changes up to 36841ba2796324507452f9854bf08b2c65836cce:

  ARM: tegra: cpuidle: Handle tick broadcasting within cpuidle core on Tegra20/30 (2019-04-18 11:32:57 +0200)

Thanks,
Thierry

----------------------------------------------------------------
ARM: tegra: Core changes for v5.2-rc1

One of these patches enables PM by default on 32-bit ARM, following the
same default that we already have on 64-bit ARM. The other patch fixes a
cosmetic issue in the cpuidle driver for Tegra20 and Tegra30.

----------------------------------------------------------------
Dmitry Osipenko (1):
      ARM: tegra: cpuidle: Handle tick broadcasting within cpuidle core on Tegra20/30

Sameer Pujar (1):
      ARM: tegra: enforce PM requirement

 arch/arm/mach-tegra/Kconfig           |  1 +
 arch/arm/mach-tegra/cpuidle-tegra20.c | 11 ++---------
 arch/arm/mach-tegra/cpuidle-tegra30.c |  9 +--------
 3 files changed, 4 insertions(+), 17 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-04-18 15:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 15:07 [GIT PULL 1/9] bus/tegra: Changes for v5.2-rc1 Thierry Reding
2019-04-18 15:07 ` [GIT PULL 2/9] soc/tegra: " Thierry Reding
2019-04-29  6:34   ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 3/9] firmware: tegra: " Thierry Reding
2019-04-29  6:34   ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 4/9] memory: " Thierry Reding
2019-04-29  6:35   ` Olof Johansson
2019-04-18 15:07 ` Thierry Reding [this message]
2019-04-29  6:35   ` [GIT PULL 5/9] ARM: tegra: Core changes " Olof Johansson
2019-04-18 15:07 ` [GIT PULL 6/9] ARM: tegra: Device tree " Thierry Reding
2019-04-28 19:39   ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 7/9] ARM: tegra: Default configuration updates " Thierry Reding
2019-04-29  6:36   ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 8/9] arm64: tegra: Device tree changes " Thierry Reding
2019-04-28 19:40   ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 9/9] arm64: tegra: Default configuration updates " Thierry Reding
2019-04-29  6:37   ` Olof Johansson
2019-04-29  6:33 ` [GIT PULL 1/9] bus/tegra: Changes " Olof Johansson

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=20190418150721.8828-5-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.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).