From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Olof Johansson" <olof@lixom.net>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the samsung-krzk tree
Date: Tue, 03 Oct 2023 16:31:19 +0200 [thread overview]
Message-ID: <e076a52f-8aeb-417a-8093-362d36573f8b@app.fastmail.com> (raw)
In-Reply-To: <50f32be6-ccbe-42b7-81bf-7509da400ba6@linaro.org>
On Tue, Oct 3, 2023, at 08:22, Krzysztof Kozlowski wrote:
> On 29/09/2023 02:25, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commit is also in the arm-soc-fixes tree as a different
>> commit (but the same patch):
>>
>> 471eed5ad217 ("arm64: defconfig: enable syscon-poweroff driver")
>>
>> This is commit
>>
>> d75e870c32f6 ("arm64: defconfig: enable syscon-poweroff driver")
>>
>> in the arm-soc-fixes tree.
>
> Hm, I did not expect this going through arm-soc, but no problem. I
> dropped it now from my tree.
Right, I was a little confused about why you sent the patch to
soc@kernel.org and had to guess between applying to fixes, to
the next branches or ignoring.
I should have asked you for confirmation here, but ended up
just merging it as it seemed harmless enough either way.
Arnd
next prev parent reply other threads:[~2023-10-03 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 0:25 Stephen Rothwell
2023-10-03 6:22 ` Krzysztof Kozlowski
2023-10-03 14:31 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-24 1:09 Stephen Rothwell
2025-11-24 7:49 ` Krzysztof Kozlowski
2024-07-10 2:33 Stephen Rothwell
2024-07-10 6:38 ` Krzysztof Kozlowski
2023-10-17 0:01 Stephen Rothwell
2023-10-17 9:42 ` Uwe Kleine-König
2023-10-17 9:50 ` Krzysztof Kozlowski
2023-08-15 2:06 Stephen Rothwell
2023-08-15 4:59 ` Krzysztof Kozlowski
2023-06-29 22:46 Stephen Rothwell
2023-07-01 7:57 ` Krzysztof Kozlowski
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=e076a52f-8aeb-417a-8093-362d36573f8b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®