From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Kaustabh Chakraborty <kauschluss@disroot.org>,
Rob Herring <robh@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sergey Lisov <sleirsgoevy@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add chip ID for Exynos7870 SoC
Date: Tue, 4 Feb 2025 18:13:26 +0000 [thread overview]
Message-ID: <20250204-stump-irritably-9a888742b1f7@spud> (raw)
In-Reply-To: <339ea40f-6bc7-42ad-a5c2-f57b3be8cc39@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On Tue, Feb 04, 2025 at 08:53:31AM +0100, Krzysztof Kozlowski wrote:
> On 03/02/2025 21:32, Kaustabh Chakraborty wrote:
> > This patch series is a part of Exynos7870 upstreaming.
> >
> > Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
> > ---
> > Kaustabh Chakraborty (2):
> > dt-bindings: hwinfo: samsung,exynos-chipid: add exynos7870-chipid compatible
> > soc: samsung: exynos-chipid: add support for exynos7870
> >
> > Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml | 1 +
> > drivers/soc/samsung/exynos-chipid.c | 1 +
> > 2 files changed, 2 insertions(+)
>
> When I asked to split, I said per subsystem. Soc is one subsystem.
> Everything targeting SoC should be in one patchset. get_maintainers.pl
> tells the name of the subsystem and its maintainers.
>
> If there is going to be resend/new version, combine patchsets for soc
> into one patchset (just like the example I gave last time).
And please send patches to the address people list in maintainers, don't
modify the addresses.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-04 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 20:32 [PATCH 0/2] Add chip ID for Exynos7870 SoC Kaustabh Chakraborty
2025-02-03 20:32 ` [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: add exynos7870-chipid compatible Kaustabh Chakraborty
2025-02-03 20:32 ` [PATCH 2/2] soc: samsung: exynos-chipid: add support for exynos7870 Kaustabh Chakraborty
2025-02-04 7:53 ` [PATCH 0/2] Add chip ID for Exynos7870 SoC Krzysztof Kozlowski
2025-02-04 18:13 ` Conor Dooley [this message]
2025-02-04 19:29 ` Kaustabh Chakraborty
2025-02-05 7:48 ` 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=20250204-stump-irritably-9a888742b1f7@spud \
--to=conor@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kauschluss@disroot.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sleirsgoevy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox