linux-kernel - Re: linux-next: manual merge of the phy-next tree with the samsung-krzk tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a1b7ce4bce1826e9c231677bb221aa44dc842e24.camel@linaro.org>
Date: Wed, 24 Jul 2024 09:57:08 +0100
From: André Draszik <andre.draszik@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Kishon Vijay Abraham I
	 <kishon@...nel.org>, Vinod Koul <vkoul@...nel.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Krzysztof Kozlowski
	 <krzysztof.kozlowski@...aro.org>, Linux Kernel Mailing List
	 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
	 <linux-next@...r.kernel.org>, Peter Griffin <peter.griffin@...aro.org>
Subject: Re: linux-next: manual merge of the phy-next tree with the
 samsung-krzk tree

Hi Stephen,

On Wed, 2024-07-24 at 09:14 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Wed, 3 Jul 2024 14:19:32 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > 
> > Today's linux-next merge of the phy-next tree got a conflict in:
> > 
> >   include/linux/soc/samsung/exynos-regs-pmu.h
> > 
> > between commit:
> > 
> >   85863cee8ce0 ("soc: samsung: exynos-pmu: add support for PMU_ALIVE non atomic registers")
> > 
> > from the samsung-krzk tree and commit:
> > 
> >   32267c29bc7d ("phy: exynos5-usbdrd: support Exynos USBDRD 3.1 combo phy (HS & SS)")
> > 
> > from the phy-next tree.
> > 
> > I fixed it up (see below) and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging.  You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
> > 
> > diff --cc include/linux/soc/samsung/exynos-regs-pmu.h
> > index f411c176536d,6765160eaab2..000000000000
> > --- a/include/linux/soc/samsung/exynos-regs-pmu.h
> > +++ b/include/linux/soc/samsung/exynos-regs-pmu.h
> > @@@ -657,8 -657,8 +657,12 @@@
> >   #define EXYNOS5433_PAD_RETENTION_UFS_OPTION			(0x3268)
> >   #define EXYNOS5433_PAD_RETENTION_FSYSGENIO_OPTION		(0x32A8)
> >   
> >  +/* For Tensor GS101 */
> >  +#define GS101_SYSIP_DAT0					(0x810)
> >  +#define GS101_SYSTEM_CONFIGURATION				(0x3A00)
> >  +
> > + /* For GS101 */
> > + #define GS101_PHY_CTRL_USB20					0x3eb0
> > + #define GS101_PHY_CTRL_USBDP					0x3eb4
> > + 
> >   #endif /* __LINUX_SOC_EXYNOS_REGS_PMU_H */
> 
> This is now a conflict between he phy-next tree and Linus' tree.

What's the way to resolve this? Can I do something?

Cheers,
Andre'