All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PULL] memory: tegra: Changes for v5.14-rc1
Date: Thu, 3 Jun 2021 21:45:01 +0200	[thread overview]
Message-ID: <a4126d48-f5fa-d20c-9874-fc8ac78febb0@canonical.com> (raw)
In-Reply-To: <20210603143739.787957-1-thierry.reding@gmail.com>

On 03/06/2021 16:37, Thierry Reding wrote:
> Hi Krzysztof,
> 
> The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
> 
>   Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.14-memory
> 
> for you to fetch changes up to b4f74b59b99fab61ab97fc0e506f349579d8fefc:
> 
>   memory: tegra30-emc: Use devm_tegra_core_dev_init_opp_table() (2021-06-03 14:24:03 +0200)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> memory: tegra: Changes for v5.14-rc1
> 
> This stable tag contains Dmitry's power domain work, including all the
> necessary dependencies from the regulator, clock and ARM SoC trees.
> 
> ----------------------------------------------------------------
> Dmitry Osipenko (18):
>       clk: tegra30: Use 300MHz for video decoder by default
>       clk: tegra: Fix refcounting of gate clocks
>       clk: tegra: Ensure that PLLU configuration is applied properly
>       clk: tegra: Halve SCLK rate on Tegra20
>       clk: tegra: Don't allow zero clock rate for PLLs
>       clk: tegra: cclk: Handle thermal DIV2 CPU frequency throttling
>       clk: tegra: Mark external clocks as not having reset control
>       clk: tegra: Don't deassert reset on enabling clocks
>       regulator: core: Add regulator_sync_voltage_rdev()
>       soc/tegra: regulators: Bump voltages on system reboot
>       soc/tegra: Add stub for soc_is_tegra()
>       soc/tegra: Add devm_tegra_core_dev_init_opp_table()
>       soc/tegra: fuse: Add stubs needed for compile-testing
>       clk: tegra: Add stubs needed for compile-testing
>       memory: tegra: Fix compilation warnings on 64bit platforms
>       memory: tegra: Enable compile testing for all drivers
>       memory: tegra20-emc: Use devm_tegra_core_dev_init_opp_table()
>       memory: tegra30-emc: Use devm_tegra_core_dev_init_opp_table()
> 
> Thierry Reding (3):
>       Merge branch 'for-5.14/regulator' into for-5.14/soc
>       Merge branch 'for-5.14/clk' into for-5.14/memory
>       Merge branch 'for-5.14/soc' into for-5.14/memory
> 

Thanks, pulled.

Best regards,
Krzysztof

  reply	other threads:[~2021-06-03 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 14:37 [PULL] memory: tegra: Changes for v5.14-rc1 Thierry Reding
2021-06-03 19:45 ` Krzysztof Kozlowski [this message]
2021-06-03 19:56 ` Dmitry Osipenko
2021-06-04  9:32   ` Thierry Reding
2021-06-04 12:51     ` Dmitry Osipenko
2021-06-07  8:28       ` Krzysztof Kozlowski
2021-06-07 13:26         ` Thierry Reding
2021-06-07 13:41           ` Dmitry Osipenko

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=a4126d48-f5fa-d20c-9874-fc8ac78febb0@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=digetx@gmail.com \
    --cc=linux-kernel@vger.kernel.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.