mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bod@kernel.org>
To: Vinod Koul <vkoul@kernel.org>, Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>
Subject: Re: linux-next: manual merge of the phy-next tree with the v4l-dvb tree
Date: Fri, 2 Oct 2026 09:46:41 +0100	[thread overview]
Message-ID: <c60ae061-45fe-483d-a849-3c50cce9d905@kernel.org> (raw)
In-Reply-To: <ar9Vm-VPzqhtC8SQ@parshuram>

On 02/10/2026 07:56, Vinod Koul wrote:
> On 02-10-26, 07:33, Krzysztof Kozlowski wrote:
>> On 01/10/2026 16:37, Mark Brown wrote:
>>> Hi all,
>>>
>>> Today's linux-next merge of the phy-next tree got a conflict in:
>>>
>>>    Documentation/devicetree/bindings/phy/qcom,x1e80100-csi2-phy.yaml
>>>
>>> between commits:
>>>
>>>    42b96f94929c9 ("dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema")
>>>    a93b9de71466f ("dt-bindings: phy: qcom,x1e80100-csi2-phy: Add Glymur compatible")
>>>
>>> from the v4l-dvb tree and commit:
>>
>> Why were these taken via v4l/media tree?
> 
> This is even worse. Immutable branch was provided, so people can pull.
> Looks like folks cherry-picked instead. They need to fix it...
> 
>>
>>>
>>>    3b0140f37d25b ("dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema")
>>>
>>> from the phy-next tree.
>>>
>>
>>
>> Best regards,
>> Krzysztof
> 
> --
> ~Vinod

Hmm I did a git merge on your provided branch.. I did a subsequent 
rebase on linux-media/next though so that rewrote the git history. I 
should have rebased, merged and then cherry-picked what was go to into 
linux-media.

That's completely my error, I forgot to isolate the merge when rebasing.

If its OK with you I'll ask Mauro to take the version version in 
linux-media ?

---
bod

  reply	other threads:[~2026-10-02  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 14:37 Mark Brown
2026-10-02  5:33 ` Krzysztof Kozlowski
2026-10-02  6:56   ` Vinod Koul
2026-10-02  8:46     ` Bryan O'Donoghue [this message]
2026-10-02  8:30   ` 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=c60ae061-45fe-483d-a849-3c50cce9d905@kernel.org \
    --to=bod@kernel.org \
    --cc=broonie@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=kishon@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nihal.gupta@oss.qualcomm.com \
    --cc=vkoul@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

all inboxes | Powered by JetHome®