From: Bryan O'Donoghue <bod@kernel.org>
To: George Neacsu <geocausa@gmail.com>
Cc: Vinod Koul <vkoul@kernel.org>, David Heidelberg <david@ixit.cz>,
Neil Armstrong <neil.armstrong@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-phy@lists.infradead.org, linux-media@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 2/4] phy: qcom-mipi-csi2: Add C-PHY support for X1E80100
Date: Fri, 16 Oct 2026 11:12:33 +0100 [thread overview]
Message-ID: <30989671-7159-4b4f-bbf7-29303a9e13ea@kernel.org> (raw)
In-Reply-To: <20261016100621.427612-1-geocausa@gmail.com>
On 16/10/2026 11:06, George Neacsu wrote:
> Hi Bryan,
>
> Thanks for the reviews, and thanks to Loic as well.
>
> The series is on next-20261015. There, phy-qcom-mipi-csi2-3ph-dphy.c is
> blob 966d79c98, the same as on the media-committers next branch
Series doesn't apply to linux-next or phy-next - given we are at -rc7
linux-next is probably better, after -rc7 phy-next is best.
Either -next:
[~/Development/worktree/bod-media-committers]$ git fetch linux-next
*[bod-qcom-media-committers]
[~/Development/worktree/bod-media-committers]$ git reset --hard
linux-next/master
*[bod-qcom-media-committers]
HEAD is now at b810335a0699d Add linux-next specific files for 20261015
[~/Development/worktree/bod-media-committers]$ b4 shazam
20261015-x1e-cphy-rfc-v1-0-1f3fa9af940a@gmail.com
*[bod-qcom-media-committers]
Looking up
https://lore.kernel.org/all/20261015-x1e-cphy-rfc-v1-0-1f3fa9af940a@gmail.com/
Grabbing thread from
lore.kernel.org/all/20261015-x1e-cphy-rfc-v1-0-1f3fa9af940a@gmail.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 15 messages in the thread
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
✗ [PATCH RFC 1/4] phy: Add MIPI C-PHY mode and configuration options
+ Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> (✓
DKIM/linaro.org)
✗ [PATCH RFC 2/4] phy: qcom-mipi-csi2: Add C-PHY support for X1E80100
✗ [PATCH RFC 3/4] media: qcom: camss: csid-680: Select C-PHY in the
receiver
+ Reviewed-by: Loic Poulain <loic.poulain@oss.qualcomm.com> (✓
DKIM/oss.qualcomm.com)
✗ [PATCH RFC 4/4] media: qcom: camss: Configure C-PHY through the PHY API
---
✗ No key: ed25519/geocausa@gmail.com
---
Total patches: 4
---
Applying: phy: Add MIPI C-PHY mode and configuration options
Applying: phy: qcom-mipi-csi2: Add C-PHY support for X1E80100
Applying: media: qcom: camss: csid-680: Select C-PHY in the receiver
Applying: media: qcom: camss: Configure C-PHY through the PHY API
Patch failed at 0004 media: qcom: camss: Configure C-PHY through the PHY API
error: patch failed: drivers/media/platform/qcom/camss/camss-csiphy.c:329
error: drivers/media/platform/qcom/camss/camss-csiphy.c: patch does not
apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am
--abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Or -phy:
[~/Development/worktree/bod-media-committers]$ git fetch phy
*[bod-qcom-media-committers]
From git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy
c7f2322431cb6..8f56fdf3d8cb9 next -> phy/next
[~/Development/worktree/bod-media-committers]$ git reset --hard phy/next
*[bod-qcom-media-committers]
Updating files: 100% (16814/16814), done.
HEAD is now at 8f56fdf3d8cb9 phy: tegra: Add support for Tegra238 XUSB
pad controller
[~/Development/worktree/bod-media-committers]$ git am --abort
*[bod-qcom-media-committers]
warning: You seem to have moved HEAD since the last 'am' failure.
Not rewinding to ORIG_HEAD
[~/Development/worktree/bod-media-committers]$ b4 shazam
20261015-x1e-cphy-rfc-v1-0-1f3fa9af940a@gmail.com
*[bod-qcom-media-committers]
Looking up
https://lore.kernel.org/all/20261015-x1e-cphy-rfc-v1-0-1f3fa9af940a@gmail.com/
Grabbing thread from
lore.kernel.org/all/20261015-x1e-cphy-rfc-v1-0-1f3fa9af940a@gmail.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 15 messages in the thread
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
✗ [PATCH RFC 1/4] phy: Add MIPI C-PHY mode and configuration options
+ Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> (✓
DKIM/linaro.org)
✗ [PATCH RFC 2/4] phy: qcom-mipi-csi2: Add C-PHY support for X1E80100
✗ [PATCH RFC 3/4] media: qcom: camss: csid-680: Select C-PHY in the
receiver
+ Reviewed-by: Loic Poulain <loic.poulain@oss.qualcomm.com> (✓
DKIM/oss.qualcomm.com)
✗ [PATCH RFC 4/4] media: qcom: camss: Configure C-PHY through the PHY API
---
✗ No key: ed25519/geocausa@gmail.com
---
Total patches: 4
---
Applying: phy: Add MIPI C-PHY mode and configuration options
Applying: phy: qcom-mipi-csi2: Add C-PHY support for X1E80100
Applying: media: qcom: camss: csid-680: Select C-PHY in the receiver
Applying: media: qcom: camss: Configure C-PHY through the PHY API
Patch failed at 0004 media: qcom: camss: Configure C-PHY through the PHY API
error: patch failed: drivers/media/platform/qcom/camss/camss-csiphy.c:329
error: drivers/media/platform/qcom/camss/camss-csiphy.c: patch does not
apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am
--abort".
hint: Disable this message with "git config set advice.mergeConflict false"
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-16 10:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 22:20 [PATCH RFC 0/4] phy: qcom-mipi-csi2: C-PHY for X1E80100 George Neacsu via B4 Relay
2026-10-15 22:20 ` [PATCH RFC 1/4] phy: Add MIPI C-PHY mode and configuration options George Neacsu via B4 Relay
2026-10-16 9:13 ` Bryan O'Donoghue
2026-10-16 9:24 ` Loic Poulain
2026-10-15 22:20 ` [PATCH RFC 2/4] phy: qcom-mipi-csi2: Add C-PHY support for X1E80100 George Neacsu via B4 Relay
2026-10-16 9:29 ` Bryan O'Donoghue
2026-10-16 10:06 ` George Neacsu
2026-10-16 10:12 ` Bryan O'Donoghue [this message]
2026-10-16 9:59 ` Nihal Kumar Gupta
2026-10-16 10:06 ` George Neacsu
2026-10-16 10:23 ` Konrad Dybcio
2026-10-15 22:20 ` [PATCH RFC 3/4] media: qcom: camss: csid-680: Select C-PHY in the receiver George Neacsu via B4 Relay
2026-10-16 7:50 ` Loic Poulain
2026-10-15 22:20 ` [PATCH RFC 4/4] media: qcom: camss: Configure C-PHY through the PHY API George Neacsu via B4 Relay
2026-10-16 7:56 ` Loic Poulain
2026-10-16 8:59 ` Bryan O'Donoghue
2026-10-16 9:09 ` Bryan O'Donoghue
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=30989671-7159-4b4f-bbf7-29303a9e13ea@kernel.org \
--to=bod@kernel.org \
--cc=david@ixit.cz \
--cc=geocausa@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=vkoul@kernel.org \
--cc=vladimir.zapolskiy@linaro.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