From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Mike Rapoport <mike@compulab.co.il>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: linux-next: manual merge of the sound tree with the tree
Date: Mon, 02 Nov 2009 11:12:52 +0100 [thread overview]
Message-ID: <s5hljipxmjf.wl%tiwai@suse.de> (raw)
In-Reply-To: <20091102122222.542dac88.sfr@canb.auug.org.au>
At Mon, 2 Nov 2009 12:22:22 +1100,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> Today's linux-next merge of the sound tree got a conflict in
> arch/arm/mach-omap2/board-omap3evm.c between commit
> fa48a99192e3ee862f6d26c5248347c772b33b84 ("omap3: evm: initialize vmmc
> and vmmc_aux regulators") from the omap tree and commit
> f8d9aad96d0d7b57d0bf2e4de21fdda3a42f4449 ("OMAP: Platform support for
> twl4030_codec MFD") from the sound tree.
>
> Just overlapping additions. I fixed it up (see below) and can carry the
> fix as necessary.
Thanks Stephen.
Since this is a simple conflict, as now I'll keep sound tree as is.
Let me know if any severe conflict comes out.
thanks,
Takashi
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc arch/arm/mach-omap2/board-omap3evm.c
> index 660ef8c,d9a6103..0000000
> --- a/arch/arm/mach-omap2/board-omap3evm.c
> +++ b/arch/arm/mach-omap2/board-omap3evm.c
> @@@ -247,8 -211,7 +255,9 @@@ static struct twl4030_platform_data oma
> .madc = &omap3evm_madc_data,
> .usb = &omap3evm_usb_data,
> .gpio = &omap3evm_gpio_data,
> + .vmmc1 = &omap3evm_vmmc1,
> + .vsim = &omap3evm_vsim,
> + .codec = &omap3evm_codec_data,
> };
>
> static struct i2c_board_info __initdata omap3evm_i2c_boardinfo[] = {
>
prev parent reply other threads:[~2009-11-02 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 1:22 linux-next: manual merge of the sound tree with the tree Stephen Rothwell
2009-11-02 10:12 ` Takashi Iwai [this message]
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=s5hljipxmjf.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=peter.ujfalusi@nokia.com \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
/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