From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the samsung-krzk tree
Date: Tue, 15 Aug 2023 06:59:06 +0200 [thread overview]
Message-ID: <c27d68eb-bd7b-6e85-0d7c-d4ff8bb96687@linaro.org> (raw)
In-Reply-To: <20230815120622.528613e2@canb.auug.org.au>
On 15/08/2023 04:06, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in arm-soc tree as a different commit
> (but the same patch):
>
> 3027df7e739c ("ARM: s5pv210: Explicitly include correct DT includes")
>
> This is commit
>
> 8787bc51a7e2 ("ARM: s5pv210: Explicitly include correct DT includes")
>
> in the arm-soc tree.
Thanks, it was expected.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-15 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 2:06 linux-next: duplicate patch in the samsung-krzk tree Stephen Rothwell
2023-08-15 4:59 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 0:25 Stephen Rothwell
2023-10-03 6:22 ` Krzysztof Kozlowski
2023-10-03 14:31 ` Arnd Bergmann
2023-10-17 0:01 Stephen Rothwell
2023-10-17 9:42 ` Uwe Kleine-König
2023-10-17 9:50 ` Krzysztof Kozlowski
2024-07-10 2:33 Stephen Rothwell
2024-07-10 6:38 ` Krzysztof Kozlowski
2025-11-24 1:09 Stephen Rothwell
2025-11-24 7:49 ` 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=c27d68eb-bd7b-6e85-0d7c-d4ff8bb96687@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).