linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-omap@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Syed Rafiuddin <rafiuddin.syed@ti.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Kalle Valo <kalle.valo@iki.fi>
Subject: Re: linux-next: manual merge of the omap tree with the arm tree
Date: Mon, 24 Aug 2009 16:07:18 +0300	[thread overview]
Message-ID: <20090824130718.GC5165@atomide.com> (raw)
In-Reply-To: <20090820102004.GD12309@atomide.com>

* Tony Lindgren <tony@atomide.com> [090820 14:20]:
> * Stephen Rothwell <sfr@canb.auug.org.au> [090819 08:04]:
> > Hi all,
> > 
> > Today's linux-next merge of the omap tree got a conflict in
> > arch/arm/mach-omap2/board-4430sdp.c between commit
> > 085b54d99b8ee999e7905b8f16e201e0da8ba369 ("ARM: OMAP4: Add UART4
> > support") from the arm tree and commit
> > 4c29fa3e47342666e12e46f35f40dd90b12cd1a4 ("OMAP: remove OMAP_TAG_UART")
> > from the omap tree.
> > 
> > Just context changes (I think).  I fixed it up (see below) and can carry
> > the fix as necessary.
> 
> Thanks yeh the fix looks right. I'll take a look if I can squeeze something
> like that into my queue so the merge conflict disappears.

The merge conflict should be gone now, Kevin realized we don't need the
platform_data any longer. Will remove that for board-4430sdp.c and serial.h
as a fix once the other pending changes have been merged.
 
> Regards,
> 
> Tony
> 
> > -- 
> > Cheers,
> > Stephen Rothwell                    sfr@canb.auug.org.au
> > 
> > diff --cc arch/arm/mach-omap2/board-4430sdp.c
> > index 1b22307,646079f..0000000
> > --- a/arch/arm/mach-omap2/board-4430sdp.c
> > +++ b/arch/arm/mach-omap2/board-4430sdp.c
> > @@@ -38,8 -38,8 +38,8 @@@ static struct platform_device *sdp4430_
> >   	&sdp4430_lcd_device,
> >   };
> >   
> > - static struct omap_uart_config sdp4430_uart_config __initdata = {
> > + static struct omap_uart_platform_data sdp4430_uart_config __initdata = {
> >  -	.enabled_uarts	= (1 << 0) | (1 << 1) | (1 << 2),
> >  +	.enabled_uarts	= (1 << 0) | (1 << 1) | (1 << 2) | (1 << 3),
> >   };
> >   
> >   static struct omap_lcd_config sdp4430_lcd_config __initdata = {
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  parent reply	other threads:[~2009-08-24 13:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  5:04 linux-next: manual merge of the omap tree with the arm tree Stephen Rothwell
2009-08-20 10:20 ` Tony Lindgren
2009-08-20 13:03   ` Shilimkar, Santosh
2009-08-20 13:13     ` Shilimkar, Santosh
2009-08-20 13:55       ` Tony Lindgren
2009-08-24 13:07   ` Tony Lindgren [this message]
2009-08-24 13:14     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2010-12-26 22:41 Stephen Rothwell
2010-07-08  1:37 Stephen Rothwell
2010-07-08 10:14 ` Tony Lindgren
2010-07-04 23:20 Stephen Rothwell
2010-07-05  1:46 ` Nicolas Pitre
2010-07-05  7:14   ` Stephen Rothwell
2010-07-05 13:44     ` Tony Lindgren
2010-02-04 23:20 Stephen Rothwell
2010-02-04 23:30 ` Tony Lindgren
2010-02-05  0:16   ` Stephen Rothwell
2010-02-05  4:04     ` Tony Lindgren
2010-02-15 15:03       ` Russell King
2010-02-17 19:33         ` Tony Lindgren
2009-05-28  4:31 Stephen Rothwell
2009-05-28  6:25 ` Shilimkar, Santosh
2009-05-28  6:34   ` Stephen Rothwell
2009-05-28  6:40     ` Shilimkar, Santosh

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=20090824130718.GC5165@atomide.com \
    --to=tony@atomide.com \
    --cc=kalle.valo@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rafiuddin.syed@ti.com \
    --cc=rmk@arm.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).