From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org
Cc: linux-kernel@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [GIT PULL 1/2] memory: drivers for v5.17
Date: Thu, 27 Jan 2022 10:33:10 +0100 [thread overview]
Message-ID: <1812c271-0a6f-2ebf-e329-4d3c0e34024c@canonical.com> (raw)
In-Reply-To: <724c16d2-5afc-4d41-8d84-3ba570d14cee@canonical.com>
On 23/01/2022 13:00, Krzysztof Kozlowski wrote:
> On 24/12/2021 12:11, Krzysztof Kozlowski wrote:
>> The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
>>
>> Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
>>
>> are available in the Git repository at:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git tags/memory-controller-drv-5.17
>>
>> for you to fetch changes up to de369801658a9a54759ac011af770e8c01d9db7f:
>>
>> Merge branch 'for-v5.17/tegra-mc' into mem-ctrl-next (2021-12-22 12:59:03 +0100)
>>
>> ----------------------------------------------------------------
>> Memory controller drivers for v5.17
>>
>> 1. Minor improvements: Mediatek SMI, Freescale/NXP IFC, Tegra20 and
>> Tegra30.
>> 2. Convert Freescale/NXP IFC bindings to dtschema.
>>
>> ----------------------------------------------------------------
>> AngeloGioacchino Del Regno (1):
>> memory: mtk-smi: Use ARRAY_SIZE to define MTK_SMI_CLK_NR_MAX
>>
>> Dmitry Osipenko (2):
>> memory: tegra30-emc: Print additional memory info
>> memory: tegra20-emc: Correct memory device mask
>>
>> Jason Wang (1):
>> memory: brcmstb_dpfe: fix typo in a comment
>>
>> Krzysztof Kozlowski (1):
>> Merge branch 'for-v5.17/tegra-mc' into mem-ctrl-next
>>
>> Li Yang (2):
>> dt-bindings: memory: fsl: convert ifc binding to yaml schema
>> memory: fsl_ifc: populate child devices without relying on simple-bus
>>
>> Rikard Falkeborn (1):
>> memory: tegra: Constify struct thermal_cooling_device_ops
>>
>
> Arnd, Olof,
>
> I think this one was not pulled by you. Any chances of sending this to
> Linus past 5.17-rc1? If not, could you pull it as v5.18 material?
I'll send all this as v5.18 material, so this pull-req can be skipped.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-01-27 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 11:11 [GIT PULL 1/2] memory: drivers for v5.17 Krzysztof Kozlowski
2021-12-24 11:11 ` [GIT PULL 2/2] memory: omap: " Krzysztof Kozlowski
2021-12-30 15:49 ` Miquel Raynal
2021-12-31 12:18 ` Miquel Raynal
2022-01-23 12:00 ` [GIT PULL 1/2] memory: " Krzysztof Kozlowski
2022-01-27 9:33 ` Krzysztof Kozlowski [this message]
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=1812c271-0a6f-2ebf-e329-4d3c0e34024c@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=linux-kernel@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