From: Krzysztof Kozlowski <krzk@kernel.org>
To: Atanas Filipov <atanas.filipov@oss.qualcomm.com>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org, bod@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/4] dt-bindings: media: qcom: Add JPEG encoder binding
Date: Sat, 13 Jun 2026 20:42:01 +0200 [thread overview]
Message-ID: <20260613-fair-ultraviolet-dog-fece5e@quoll> (raw)
In-Reply-To: <20260612194417.1737009-2-atanas.filipov@oss.qualcomm.com>
On Fri, Jun 12, 2026 at 10:44:14PM +0300, Atanas Filipov wrote:
> Add device-tree binding for the standalone Qualcomm JPEG encoder
> hardware block (separate from CAMSS media pipelines).
>
> Document required resources briefly and scope initial support to
> currently used compatibles in this series, including SM8250,
> QCM6490, and SM8550 class platforms.
>
> Signed-off-by: Atanas Filipov <atanas.filipov@oss.qualcomm.com>
> ---
> .../bindings/media/qcom,jpeg-encoder.yaml | 142 ++++++++++++++++++
You already sent v1 and you received review. Quite a lot of comments.
Please do not send duplicated work, but address the feedback.
Then version your patches correctly, so the toolset will work. Sending
duplicated work is not making the review easy. I am dropping this from
DT patchwork.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-13 18:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 19:44 [PATCH v1 0/4] This series adds support for the Qualcomm JPEG V4L2 mem2mem encoder Atanas Filipov
2026-06-12 19:44 ` [PATCH v1 1/4] dt-bindings: media: qcom: Add JPEG encoder binding Atanas Filipov
2026-06-12 19:57 ` sashiko-bot
2026-06-12 20:42 ` Frank Li
2026-06-12 23:17 ` Bryan O'Donoghue
2026-06-12 23:38 ` Bryan O'Donoghue
2026-06-13 18:42 ` Krzysztof Kozlowski [this message]
2026-07-13 7:43 ` Atanas Filipov
2026-06-23 6:41 ` Luca Weiss
2026-06-12 19:44 ` [PATCH v1 2/4] arm64: dts: qcom: sm8550: Add JPEG encoder node Atanas Filipov
2026-06-12 20:06 ` sashiko-bot
2026-06-12 23:14 ` Bryan O'Donoghue
2026-06-13 9:24 ` Atanas Filipov
2026-06-13 9:52 ` Bryan O'Donoghue
2026-06-13 11:16 ` Atanas Filipov
2026-06-14 1:13 ` Bryan O'Donoghue
2026-06-19 14:38 ` Konrad Dybcio
2026-06-19 14:57 ` Vladimir Zapolskiy
2026-06-12 23:52 ` Bryan O'Donoghue
2026-06-13 16:05 ` Atanas Filipov
2026-06-14 0:53 ` Bryan O'Donoghue
2026-06-14 21:28 ` Dmitry Baryshkov
2026-06-12 19:44 ` [PATCH v1 3/4] arm64: dts: qcom: sm8250: " Atanas Filipov
2026-06-12 19:44 ` [PATCH v1 4/4] media: qcom: jpeg: Add Qualcomm JPEG V4L2 encoder Atanas Filipov
2026-06-12 20:23 ` sashiko-bot
2026-06-12 20:53 ` Frank Li
2026-06-13 18:43 ` Krzysztof Kozlowski
2026-07-13 7:50 ` Atanas Filipov
2026-06-25 13:43 ` [PATCH v1 0/4] This series adds support for the Qualcomm JPEG V4L2 mem2mem encoder Atanas Filipov
2026-06-25 13:53 ` Krzysztof Kozlowski
2026-07-13 7:52 ` Atanas Filipov
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=20260613-fair-ultraviolet-dog-fece5e@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=atanas.filipov@oss.qualcomm.com \
--cc=bod@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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