All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-omap@vger.kernel.org, Richard Woodruff <r-woodruff2@ti.com>,
	linux-next@vger.kernel.org, Felipe Balbi <felipe.balbi@nokia.com>,
	Wim Van Sebroeck <wim@iguana.be>,
	Syed Mohammed Khasim <khasim@ti.com>,
	David Brownell <david-b@pacbell.net>
Subject: [PATCH] ARM: OMAP: Revert omap3 WDT changes to avoid merge conflict (Re: linux-next: manual merge of the arm tree)
Date: Tue, 14 Oct 2008 13:30:24 -0700	[thread overview]
Message-ID: <20081014203017.GH8150@atomide.com> (raw)
In-Reply-To: <20081014200805.GF8150@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

* Tony Lindgren <tony@atomide.com> [081014 13:09]:
> * David Brownell <david-b@pacbell.net> [081014 11:53]:
> > On Tuesday 14 October 2008, Russell King wrote:
> > > Since the OMAP updates I merged from Tony are already broken due to
> > > missing definitions, and I'm not getting any response from Tony on
> > > fixing those,
> 
> I just sent you a fix for that few hours ago.
> 
> > Probably has to do with his travel plans, which he mentioned
> > last week (Thursday?).  I think he's back online in the next
> > day or two.
> > 
> > 
> > > I will be dropping the problematical updates so we can 
> > > at least keep mainline OMAP in a buildable state.  That seems to mean
> > > dropping the new OMAP3 support.
> 
> Yes, I'm back online. And please don't drop these patches, sounds
> like this is a trivial merge issue.

And here's the patch for Russell to avoid the merge conflict.
Also in Russell's patch tracking system as patch 5302/1.

> 
> Regards,
> 
> Tony

[-- Attachment #2: wdt.patch --]
[-- Type: text/x-diff, Size: 894 bytes --]

From: Tony Lindgren <tony@atomide.com>
Date: Tue, 14 Oct 2008 13:25:20 -0700
Subject: [PATCH] ARM: OMAP: Revert omap3 WDT changes to avoid merge conflict

With the upcoming WDT patches OMAP_WDT_BASE is no longer needed
in devices.c. Revert some earlier omap3 changes to avoid merge
conflicts with the WDT patches.

Signed-off-by: Tony Lindgren <tony@atomide.com>

--- a/arch/arm/plat-omap/devices.c
+++ b/arch/arm/plat-omap/devices.c
@@ -399,17 +399,8 @@ static inline void omap_init_uwire(void) {}
 
 #if	defined(CONFIG_OMAP_WATCHDOG) || defined(CONFIG_OMAP_WATCHDOG_MODULE)
 
-#if defined(CONFIG_ARCH_OMAP34XX)
-#define	OMAP_WDT_BASE		0x48314000
-#elif defined(CONFIG_ARCH_OMAP24XX)
-
-#ifdef CONFIG_ARCH_OMAP2430
-/* WDT2 */
-#define	OMAP_WDT_BASE		0x49016000
-#else
+#ifdef CONFIG_ARCH_OMAP24XX
 #define	OMAP_WDT_BASE		0x48022000
-#endif
-
 #else
 #define	OMAP_WDT_BASE		0xfffeb000
 #endif

  reply	other threads:[~2008-10-14 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  2:27 linux-next: manual merge of the arm tree Stephen Rothwell
2008-10-14  7:59 ` Russell King
2008-10-14  8:07   ` David Brownell
2008-10-14 20:08     ` Tony Lindgren
2008-10-14 20:30       ` Tony Lindgren [this message]
2008-10-14 20:40         ` [PATCH] ARM: OMAP: Revert omap3 WDT changes to avoid merge conflict (Re: linux-next: manual merge of the arm tree) Russell King

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=20081014203017.GH8150@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=khasim@ti.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=r-woodruff2@ti.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=sfr@canb.auug.org.au \
    --cc=wim@iguana.be \
    /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.