From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Peter Griffin" <peter.griffin@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
linux-samsung-soc@vger.kernel.org,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Sam Protsenko" <semen.protsenko@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Ivaylo Ivanov" <ivo.ivanov.ivanov1@gmail.com>,
"Igor Belwon" <igor.belwon@mentallysanemainliners.org>,
"Denzeel Oliva" <wachiturroxd150@gmail.com>,
"Kaustabh Chakraborty" <kauschluss@disroot.org>
Subject: Re: Any pending patches on me for Samsung SoC? Closing applying cycle
Date: Thu, 06 Mar 2025 14:03:32 +0000 [thread overview]
Message-ID: <55501e08b586c9bb1178be658299207b@disroot.org> (raw)
In-Reply-To: <56288828-c767-4198-8f5c-a891d169b6cd@kernel.org>
On 2025-03-05 19:45, Krzysztof Kozlowski wrote:
> Hey,
>
> I went through my inbox and cleared my queue because I am approaching
> end of applying cycle. I think I dealt with everything and pending
> things are:
>
> 1. Exynos7870 SoC: waits for bindings,
Is this possible to be merged? [1]
It's over a month old at this point, seemingly left untouched.
This one's also a build dependency for [2], as mentioned in its cover
letter.
[1] https://lore.kernel.org/all/20250204-exynos7870-bootmode-v1-1-0f17b3033c2d@disroot.org/
[2] https://lore.kernel.org/all/174100756283.1496281.12555971793250210333.robh@kernel.org/
next prev parent reply other threads:[~2025-03-06 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 19:45 Any pending patches on me for Samsung SoC? Closing applying cycle Krzysztof Kozlowski
2025-03-05 21:07 ` Ivaylo Ivanov
2025-03-05 21:47 ` Krzysztof Kozlowski
2025-03-06 14:03 ` Kaustabh Chakraborty [this message]
2025-03-06 18:07 ` Krzysztof Kozlowski
2025-03-06 18:37 ` Kaustabh Chakraborty
2025-03-06 19:42 ` 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=55501e08b586c9bb1178be658299207b@disroot.org \
--to=kauschluss@disroot.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=wachiturroxd150@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.