From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Aakarsh Jain <aakarsh.jain@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
m.szyprowski@samsung.com, andrzej.hajda@intel.com,
mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
alim.akhtar@samsung.com, robh@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: linux-samsung-soc@vger.kernel.org, aswani.reddy@samsung.com,
anindya.sg@samsung.com
Subject: Re: [PATCH 07/10] media: s5p-mfc: Modify compatible string check for SoC-specific support
Date: Thu, 7 Aug 2025 13:02:20 +0200 [thread overview]
Message-ID: <4150c213-b99a-4862-9e60-f374e40f97c8@linaro.org> (raw)
In-Reply-To: <20250807032449.92770-8-aakarsh.jain@samsung.com>
On 07/08/2025 05:24, Aakarsh Jain wrote:
> Modify the compatible string handling in the MFC driver
> to explicitly match SoC-specific identifiers.
>
> Signed-off-by: Aakarsh Jain <aakarsh.jain@samsung.com>
Please read maintainer soc profile, submitting patches in DT dir and
writing bindings. You just broke all platforms without even admitting it
and without providing rationale.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-07 11:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250807032459epcas5p1d6bd796f5b654c92372bdcc8a7926c22@epcas5p1.samsung.com>
2025-08-07 3:24 ` [PATCH 00/10] Use SoC-specific compatible string for Samsung MFC Aakarsh Jain
[not found] ` <CGME20250807032506epcas5p3a05a916da73778cce6a310bafbe1ebba@epcas5p3.samsung.com>
2025-08-07 3:24 ` [PATCH 01/10] ARM: dts: samsung: exynos3250: Use SoC-specific compatible string for MFC Aakarsh Jain
[not found] ` <CGME20250807032508epcas5p416a3af567faba6a4fe3d6f6af5c0dd80@epcas5p4.samsung.com>
2025-08-07 3:24 ` [PATCH 02/10] ARM: dts: samsung: exynos4: " Aakarsh Jain
2025-08-07 10:59 ` Krzysztof Kozlowski
2025-08-07 10:59 ` Krzysztof Kozlowski
[not found] ` <CGME20250807032511epcas5p118f9d82ef2f0dd7e433cc7f715a13d53@epcas5p1.samsung.com>
2025-08-07 3:24 ` [PATCH 03/10] ARM: dts: samsung: exynos5250: " Aakarsh Jain
[not found] ` <CGME20250807032513epcas5p224dc2883dff3610770140af0f93354cf@epcas5p2.samsung.com>
2025-08-07 3:24 ` [PATCH 04/10] ARM: dts: samsung: exynos5420: " Aakarsh Jain
[not found] ` <CGME20250807032515epcas5p294e3bb229552cdcff28fa24691c3534a@epcas5p2.samsung.com>
2025-08-07 3:24 ` [PATCH 05/10] ARM: dts: samsung: exynos5800: " Aakarsh Jain
[not found] ` <CGME20250807032518epcas5p2af27b86e19d451e5ccc9cbc9c7b676ce@epcas5p2.samsung.com>
2025-08-07 3:24 ` [PATCH 06/10] ARM: dts: samsung: s5pv210: " Aakarsh Jain
[not found] ` <CGME20250807032520epcas5p47545f2b03e29296b583248f8315abf45@epcas5p4.samsung.com>
2025-08-07 3:24 ` [PATCH 07/10] media: s5p-mfc: Modify compatible string check for SoC-specific support Aakarsh Jain
2025-08-07 11:02 ` Krzysztof Kozlowski [this message]
[not found] ` <CGME20250807032523epcas5p2a270279907bbccdb08b45f56a8c38f21@epcas5p2.samsung.com>
2025-08-07 3:24 ` [PATCH 08/10] media: s5p-mfc: Add new compatible string corresponding to S5pv210 SoC Aakarsh Jain
[not found] ` <CGME20250807032525epcas5p42f764c0b2af23d0e47e853fc5707cb46@epcas5p4.samsung.com>
2025-08-07 3:24 ` [PATCH 09/10] dt-bindings: media: s5p-mfc: Modify compatible string check for SoC-specific support Aakarsh Jain
2025-08-07 11:00 ` Krzysztof Kozlowski
[not found] ` <CGME20250807032527epcas5p488b0eed9dcb260cad4f864d9ec6e8477@epcas5p4.samsung.com>
2025-08-07 3:24 ` [PATCH 10/10] dt-bindings: media: s5p-mfc: Add SoC-specific compatible for 'samsung,mfc-v5' Aakarsh Jain
2025-08-07 11:05 ` [PATCH 00/10] Use SoC-specific compatible string for Samsung MFC 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=4150c213-b99a-4862-9e60-f374e40f97c8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=aakarsh.jain@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=andrzej.hajda@intel.com \
--cc=anindya.sg@samsung.com \
--cc=aswani.reddy@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=robh@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).