From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Pierre Gondois <pierre.gondois@arm.com>, linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob.Herring@arm.com, linux-samsung-soc@vger.kernel.org
Subject: Re: (subset) [PATCH 06/20] arm64: dts: Update cache properties for exynos
Date: Wed, 23 Nov 2022 09:20:34 +0100 [thread overview]
Message-ID: <4f4bdc95-16a2-df76-9787-df46a3b5e1eb@linaro.org> (raw)
In-Reply-To: <7681ba8e-1036-7540-5eda-417ed204d35f@arm.com>
On 22/11/2022 17:52, Pierre Gondois wrote:
> Hello Krzysztof,
>
> This patch and [1] were dropped after a bad patch management from my part.
> v1 and v2 are identical, but [2] lead to the 2 patches to be removed.
> Not willing to worsen the situation, I wanted to wait a bit before getting
> back to these 2 patches and let them be removed.
> Would it be possible to take back these 2 patches ?
>
> Regards,
> Pierre
>
> [1] https://lore.kernel.org/all/2d8b2d85-7bc6-026a-baf9-11a47171ddc5@linaro.org/
> [2] https://lore.kernel.org/all/bb36df3f-5aee-256a-4d64-eaeb9bff998e@arm.com/
>
I was expecting a resend with:
1. Fixed subject.
2. Changelog.
3. Trimmed list.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-23 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221031091951epcas5p44474924d5427c37186fa2ad6305e0ccf@epcas5p4.samsung.com>
2022-10-31 9:19 ` [PATCH 06/20] arm64: dts: Update cache properties for exynos Pierre Gondois
2022-11-02 20:21 ` (subset) " Krzysztof Kozlowski
2022-11-07 18:13 ` Krzysztof Kozlowski
2022-11-22 16:52 ` Pierre Gondois
2022-11-23 8:20 ` Krzysztof Kozlowski [this message]
2022-11-03 5:17 ` Alim Akhtar
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=4f4bdc95-16a2-df76-9787-df46a3b5e1eb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Rob.Herring@arm.com \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=robh+dt@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).