From: Bryan O'Donoghue <bod@kernel.org>
To: Atanas Filipov <atanas.filipov@oss.qualcomm.com>,
linux-media@vger.kernel.org
Cc: mchehab@kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
andersson@kernel.org, quic_vgarodia@quicinc.com,
quic_jesszhan@quicinc.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] media: qcom: jpeg: Add Qualcomm JPEG V4L2 encoder
Date: Mon, 29 Jun 2026 14:50:14 +0100 [thread overview]
Message-ID: <c7b58999-38e8-4067-8bc6-3a41cb515f6b@kernel.org> (raw)
In-Reply-To: <596dd8d5-638a-42d3-a00b-9a72f26508a9@kernel.org>
On 29/06/2026 14:48, Bryan O'Donoghue wrote:
> is after
* is faster
---
bod
next prev parent reply other threads:[~2026-06-29 13:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:17 [PATCH v3 0/4] Add Qualcomm JPEG V4L2 encoder for SM8250 Atanas Filipov
2026-06-29 12:17 ` [PATCH v3 1/4] media: qcom: camss: populate child platform devices Atanas Filipov
2026-06-29 12:30 ` sashiko-bot
2026-06-29 13:41 ` Vladimir Zapolskiy
2026-06-29 12:17 ` [PATCH v3 2/4] dt-bindings: media: qcom: Add JPEG encoder binding Atanas Filipov
2026-06-29 12:25 ` sashiko-bot
2026-06-29 12:58 ` Dmitry Baryshkov
2026-06-29 13:38 ` Vladimir Zapolskiy
2026-06-30 13:19 ` Bryan O'Donoghue
2026-06-30 13:32 ` Vladimir Zapolskiy
2026-06-30 20:24 ` Bryan O'Donoghue
2026-06-30 21:02 ` Vladimir Zapolskiy
2026-06-29 13:41 ` Rob Herring (Arm)
2026-06-29 12:17 ` [PATCH v3 3/4] arm64: dts: qcom: sm8250: Add JPEG encoder node Atanas Filipov
2026-06-29 12:34 ` sashiko-bot
2026-06-29 13:02 ` Dmitry Baryshkov
2026-06-29 12:17 ` [PATCH v3 4/4] media: qcom: jpeg: Add Qualcomm JPEG V4L2 encoder Atanas Filipov
2026-06-29 12:46 ` sashiko-bot
2026-06-29 13:48 ` Bryan O'Donoghue
2026-06-29 13:50 ` Bryan O'Donoghue [this message]
2026-06-30 9:13 ` Konrad Dybcio
2026-06-30 13:06 ` Dmitry Baryshkov
2026-06-30 14:14 ` Atanas Filipov
2026-07-01 0:13 ` Dmitry Baryshkov
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=c7b58999-38e8-4067-8bc6-3a41cb515f6b@kernel.org \
--to=bod@kernel.org \
--cc=andersson@kernel.org \
--cc=atanas.filipov@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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=quic_jesszhan@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--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 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.