linux-kernel - Re: linux-next: manual merge of the sound-asoc tree with the i.MX 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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 30 Sep 2010 08:52:02 +0200
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Sascha Hauer <s.hauer@...gutronix.de>
Subject: Re: linux-next: manual merge of the sound-asoc tree with the i.MX
	tree

Hello,

On Thu, Sep 30, 2010 at 08:41:40AM +0200, Uwe Kleine-König wrote:
> On Thu, Sep 30, 2010 at 11:23:02AM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the sound-asoc tree got a conflict in
> > arch/arm/mach-mx3/devices.c between commit
> > 4697bb926f43b8012ebd111ef43834f42126a0ef ("ARM: imx: dynamically allocate
> > imx-ssi devices") from the i.MX tree and commit
> > f0fba2ad1b6b53d5360125c41953b7afcd6deff0 ("ASoC: multi-component - ASoC
> > Multi-Component Support") from the sound-asoc tree.
> > 
> > The former removed that code that the latter changed.  I just used the
> > former.
> > 
> > The latter was just changing some names, so ti may be able to be
> > integrated into the former.
> I think the same problem exists for mx2.  Maybe git didn't notice as
> arch/arm/mach-mx2/devices.c was moved to arch/arm/mach-imx/devices.c
> (and merged with arch/arm/mach-mx1/devices.c)?!
> 
> I didn't test, but I guess we need the following patch squashed into the
> merge:
> 
> diff --git a/arch/arm/plat-mxc/devices/platform-imx-ssi.c b/arch/arm/plat-mxc/devices/platform-imx-ssi.c
> index 38a7a0b..6d74a25 100644
> --- a/arch/arm/plat-mxc/devices/platform-imx-ssi.c
> +++ b/arch/arm/plat-mxc/devices/platform-imx-ssi.c
> @@ -101,7 +101,7 @@ struct platform_device *__init imx_add_imx_ssi(
>  		DMARES(rx1),
>  	};
>  
> -	return imx_add_platform_device("imx-ssi", data->id,
> +	return imx_add_platform_device("imx-ssi-dai", data->id,
>  			res, ARRAY_SIZE(res),
>  			pdata, sizeof(*pdata));
>  }
I just noticed there are some more problems:

	ukl@...opus:~/gsrc/linux-2.6$ git grep \"imx-ssi[^-] next/master -- arch/arm/mach-{imx,mx*}
	next/master:arch/arm/mach-imx/clock-imx27.c:    _REGISTER_CLOCK("imx-ssi.0", NULL, ssi1_clk)
	next/master:arch/arm/mach-imx/clock-imx27.c:    _REGISTER_CLOCK("imx-ssi.1", NULL, ssi2_clk)
	next/master:arch/arm/mach-mx25/clock.c: _REGISTER_CLOCK("imx-ssi.0", NULL, ssi1_clk)
	next/master:arch/arm/mach-mx25/clock.c: _REGISTER_CLOCK("imx-ssi.1", NULL, ssi2_clk)
	next/master:arch/arm/mach-mx5/clock-mx51.c:     _REGISTER_CLOCK("imx-ssi.0", NULL, ssi1_clk)
	next/master:arch/arm/mach-mx5/clock-mx51.c:     _REGISTER_CLOCK("imx-ssi.1", NULL, ssi2_clk)

The change to clock-imx27.c got lost similar to mx2/devices.c.  When
f0fba2ad1b6b53d5360125c41953b7afcd6deff0 was commited
arch/arm/mach-mx5/clock-mx51.c and arch/arm/mach-mx25/clock.c didn't
contain the clock for imx-ssi, yet.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/