From: Tony Lindgren <tony@atomide.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with the arm-soc tree
Date: Mon, 24 Nov 2014 07:28:37 -0800 [thread overview]
Message-ID: <20141124152836.GA2817@atomide.com> (raw)
In-Reply-To: <20141124132214.2f756b6a@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> [141123 18:24]:
> Hi Mauro,
>
> Today's linux-next merge of the v4l-dvb tree got a conflict in
> arch/arm/mach-omap2/devices.c between commit e7e42b9d2a7f ("ARM:
> OMAP4+: Remove unused omap_l3_noc platform init") from the arm-soc tree
> and commit 1b65729a186b ("[media] mach-omap2: remove deprecated
> VIDEO_OMAP2 support") from the v4l-dvb tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
Oops, that's a self-inflicted merge conflict, sorry. I should have
waited a bit longer on the removal of the now unnecessary l3_init.
Anyways, the resolution is correct thanks.
Regards,
Tony
> diff --cc arch/arm/mach-omap2/devices.c
> index 492ef1607115,1b623a06cdcd..000000000000
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@@ -67,28 -67,40 +67,6 @@@ static int __init omap3_l3_init(void
> }
> omap_postcore_initcall(omap3_l3_init);
>
> - #if defined(CONFIG_VIDEO_OMAP2) || defined(CONFIG_VIDEO_OMAP2_MODULE)
> -static int __init omap4_l3_init(void)
> -{
> - int i;
> - struct omap_hwmod *oh[3];
> - struct platform_device *pdev;
> - char oh_name[L3_MODULES_MAX_LEN];
> --
> - static struct resource omap2cam_resources[] = {
> - {
> - .start = OMAP24XX_CAMERA_BASE,
> - .end = OMAP24XX_CAMERA_BASE + 0xfff,
> - .flags = IORESOURCE_MEM,
> - },
> - {
> - .start = 24 + OMAP_INTC_START,
> - .flags = IORESOURCE_IRQ,
> - /* If dtb is there, the devices will be created dynamically */
> - if (of_have_populated_dt())
> - return -ENODEV;
> -
> - /*
> - * To avoid code running on other OMAPs in
> - * multi-omap builds
> - */
> - if (!cpu_is_omap44xx() && !soc_is_omap54xx())
> - return -ENODEV;
> -
> - for (i = 0; i < L3_MODULES; i++) {
> - snprintf(oh_name, L3_MODULES_MAX_LEN, "l3_main_%d", i+1);
> -
> - oh[i] = omap_hwmod_lookup(oh_name);
> - if (!(oh[i]))
> - pr_err("could not look up %s\n", oh_name);
> -- }
> - };
> --
> - static struct platform_device omap2cam_device = {
> - .name = "omap24xxcam",
> - .id = -1,
> - .num_resources = ARRAY_SIZE(omap2cam_resources),
> - .resource = omap2cam_resources,
> - };
> - #endif
> - pdev = omap_device_build_ss("omap_l3_noc", 0, oh, 3, NULL, 0);
> -
> - WARN(IS_ERR(pdev), "could not build omap_device for %s\n", oh_name);
> -
> - return PTR_RET(pdev);
> -}
> -omap_postcore_initcall(omap4_l3_init);
> --
> #if defined(CONFIG_IOMMU_API)
>
> #include <linux/platform_data/iommu-omap.h>
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the v4l-dvb tree with the arm-soc tree
Date: Mon, 24 Nov 2014 07:28:37 -0800 [thread overview]
Message-ID: <20141124152836.GA2817@atomide.com> (raw)
In-Reply-To: <20141124132214.2f756b6a@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> [141123 18:24]:
> Hi Mauro,
>
> Today's linux-next merge of the v4l-dvb tree got a conflict in
> arch/arm/mach-omap2/devices.c between commit e7e42b9d2a7f ("ARM:
> OMAP4+: Remove unused omap_l3_noc platform init") from the arm-soc tree
> and commit 1b65729a186b ("[media] mach-omap2: remove deprecated
> VIDEO_OMAP2 support") from the v4l-dvb tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
Oops, that's a self-inflicted merge conflict, sorry. I should have
waited a bit longer on the removal of the now unnecessary l3_init.
Anyways, the resolution is correct thanks.
Regards,
Tony
> diff --cc arch/arm/mach-omap2/devices.c
> index 492ef1607115,1b623a06cdcd..000000000000
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@@ -67,28 -67,40 +67,6 @@@ static int __init omap3_l3_init(void
> }
> omap_postcore_initcall(omap3_l3_init);
>
> - #if defined(CONFIG_VIDEO_OMAP2) || defined(CONFIG_VIDEO_OMAP2_MODULE)
> -static int __init omap4_l3_init(void)
> -{
> - int i;
> - struct omap_hwmod *oh[3];
> - struct platform_device *pdev;
> - char oh_name[L3_MODULES_MAX_LEN];
> --
> - static struct resource omap2cam_resources[] = {
> - {
> - .start = OMAP24XX_CAMERA_BASE,
> - .end = OMAP24XX_CAMERA_BASE + 0xfff,
> - .flags = IORESOURCE_MEM,
> - },
> - {
> - .start = 24 + OMAP_INTC_START,
> - .flags = IORESOURCE_IRQ,
> - /* If dtb is there, the devices will be created dynamically */
> - if (of_have_populated_dt())
> - return -ENODEV;
> -
> - /*
> - * To avoid code running on other OMAPs in
> - * multi-omap builds
> - */
> - if (!cpu_is_omap44xx() && !soc_is_omap54xx())
> - return -ENODEV;
> -
> - for (i = 0; i < L3_MODULES; i++) {
> - snprintf(oh_name, L3_MODULES_MAX_LEN, "l3_main_%d", i+1);
> -
> - oh[i] = omap_hwmod_lookup(oh_name);
> - if (!(oh[i]))
> - pr_err("could not look up %s\n", oh_name);
> -- }
> - };
> --
> - static struct platform_device omap2cam_device = {
> - .name = "omap24xxcam",
> - .id = -1,
> - .num_resources = ARRAY_SIZE(omap2cam_resources),
> - .resource = omap2cam_resources,
> - };
> - #endif
> - pdev = omap_device_build_ss("omap_l3_noc", 0, oh, 3, NULL, 0);
> -
> - WARN(IS_ERR(pdev), "could not build omap_device for %s\n", oh_name);
> -
> - return PTR_RET(pdev);
> -}
> -omap_postcore_initcall(omap4_l3_init);
> --
> #if defined(CONFIG_IOMMU_API)
>
> #include <linux/platform_data/iommu-omap.h>
next prev parent reply other threads:[~2014-11-24 15:31 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 2:22 linux-next: manual merge of the v4l-dvb tree with the arm-soc tree Stephen Rothwell
2014-11-24 2:22 ` Stephen Rothwell
2014-11-24 2:22 ` Stephen Rothwell
2014-11-24 15:28 ` Tony Lindgren [this message]
2014-11-24 15:28 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 0:04 Stephen Rothwell
2020-12-08 0:04 ` Stephen Rothwell
2020-12-14 20:30 ` Stephen Rothwell
2020-12-14 20:30 ` Stephen Rothwell
2020-12-14 21:05 ` Mauro Carvalho Chehab
2020-12-14 21:05 ` Mauro Carvalho Chehab
2017-08-22 0:55 Stephen Rothwell
2017-08-22 0:55 ` Stephen Rothwell
2017-09-04 5:23 ` Stephen Rothwell
2017-09-04 5:23 ` Stephen Rothwell
2015-12-02 13:36 Mark Brown
2015-12-02 13:36 ` Mark Brown
2014-12-05 3:03 Stephen Rothwell
2014-12-05 3:03 ` Stephen Rothwell
2014-12-05 3:03 ` Stephen Rothwell
2014-12-01 2:52 Stephen Rothwell
2014-12-01 2:52 ` Stephen Rothwell
2014-12-01 2:52 ` Stephen Rothwell
2012-01-11 2:31 Stephen Rothwell
2012-01-11 2:31 ` Stephen Rothwell
2012-01-11 2:31 ` Stephen Rothwell
2012-01-11 5:08 ` Olof Johansson
2012-01-11 5:08 ` Olof Johansson
2012-01-11 8:36 ` Guennadi Liakhovetski
2012-01-11 8:36 ` Guennadi Liakhovetski
2012-01-11 10:35 ` Mauro Carvalho Chehab
2012-01-11 10:35 ` Mauro Carvalho Chehab
2012-01-11 14:50 ` Arnd Bergmann
2012-01-11 14:50 ` Arnd Bergmann
2012-01-11 15:09 ` Olof Johansson
2012-01-11 15:09 ` Olof Johansson
2012-01-11 15:57 ` Nicolas Ferre
2012-01-11 15:57 ` Nicolas Ferre
2012-01-11 16:44 ` Olof Johansson
2012-01-11 16:44 ` Olof Johansson
2012-01-11 20:47 ` Mauro Carvalho Chehab
2012-01-11 20:47 ` Mauro Carvalho Chehab
2012-01-11 16:46 ` Arnd Bergmann
2012-01-11 16:46 ` Arnd Bergmann
2012-01-11 16:58 ` Olof Johansson
2012-01-11 16:58 ` Olof Johansson
2012-01-11 17:56 ` Guennadi Liakhovetski
2012-01-11 17:56 ` Guennadi Liakhovetski
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=20141124152836.GA2817@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=hans.verkuil@cisco.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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.