All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 2/9] soc/tegra: Changes for v5.2-rc1
Date: Sun, 28 Apr 2019 23:34:19 -0700	[thread overview]
Message-ID: <20190429063419.b2tihej6inebdpu3@localhost> (raw)
In-Reply-To: <20190418150721.8828-2-thierry.reding@gmail.com>

On Thu, Apr 18, 2019 at 05:07:13PM +0200, Thierry Reding wrote:
> 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-soc
> 
> for you to fetch changes up to 6ac2a01de1700c1b6d889f02f61c4c9602573a8d:
> 
>   soc/tegra: pmc: Move powergate initialisation to probe (2019-04-17 10:32:33 +0200)
> 
> Note that this pulls in a stable branch from Philipp for the core
> acquire/release protocol changes to the reset framework.
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> soc/tegra: Changes for v5.2-rc1
> 
> Besides a couple of fixes to better cope with deferred probing, this set
> of patches also implements the acquire/release protocol for resets used
> during powergate operations. This is necessary to allow these resets to
> be temporarily shared with other devices that may also need to control
> these resets.

Merged, thanks.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 2/9] soc/tegra: Changes for v5.2-rc1
Date: Sun, 28 Apr 2019 23:34:19 -0700	[thread overview]
Message-ID: <20190429063419.b2tihej6inebdpu3@localhost> (raw)
In-Reply-To: <20190418150721.8828-2-thierry.reding@gmail.com>

On Thu, Apr 18, 2019 at 05:07:13PM +0200, Thierry Reding wrote:
> 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-soc
> 
> for you to fetch changes up to 6ac2a01de1700c1b6d889f02f61c4c9602573a8d:
> 
>   soc/tegra: pmc: Move powergate initialisation to probe (2019-04-17 10:32:33 +0200)
> 
> Note that this pulls in a stable branch from Philipp for the core
> acquire/release protocol changes to the reset framework.
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> soc/tegra: Changes for v5.2-rc1
> 
> Besides a couple of fixes to better cope with deferred probing, this set
> of patches also implements the acquire/release protocol for resets used
> during powergate operations. This is necessary to allow these resets to
> be temporarily shared with other devices that may also need to control
> these resets.

Merged, thanks.


-Olof

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

  reply	other threads:[~2019-04-29  6:34 UTC|newest]

Thread overview: 36+ 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 ` Thierry Reding
2019-04-18 15:07 ` [GIT PULL 2/9] soc/tegra: " Thierry Reding
2019-04-18 15:07   ` Thierry Reding
2019-04-29  6:34   ` Olof Johansson [this message]
2019-04-29  6:34     ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 3/9] firmware: tegra: " Thierry Reding
2019-04-18 15:07   ` Thierry Reding
2019-04-29  6:34   ` Olof Johansson
2019-04-29  6:34     ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 4/9] memory: " Thierry Reding
2019-04-18 15:07   ` Thierry Reding
2019-04-29  6:35   ` Olof Johansson
2019-04-29  6:35     ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 5/9] ARM: tegra: Core changes " Thierry Reding
2019-04-18 15:07   ` Thierry Reding
2019-04-29  6:35   ` Olof Johansson
2019-04-29  6:35     ` Olof Johansson
2019-04-18 15:07 ` [GIT PULL 6/9] ARM: tegra: Device tree " Thierry Reding
2019-04-18 15:07   ` Thierry Reding
2019-04-28 19:39   ` Olof Johansson
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-18 15:07   ` Thierry Reding
2019-04-29  6:36   ` Olof Johansson
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-18 15:07   ` Thierry Reding
2019-04-28 19:40   ` Olof Johansson
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-18 15:07   ` Thierry Reding
2019-04-29  6:37   ` Olof Johansson
2019-04-29  6:37     ` Olof Johansson
2019-04-29  6:33 ` [GIT PULL 1/9] bus/tegra: Changes " Olof Johansson
2019-04-29  6:33   ` 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=20190429063419.b2tihej6inebdpu3@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.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.