public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, eric miao <eric.y.miao@gmail.com>,
	Russell King <rmk@arm.linux.org.uk>
Subject: Re: linux-next: manual merge of the sound tree
Date: Tue, 15 Jul 2008 08:23:26 +0200	[thread overview]
Message-ID: <s5hk5fnwtr5.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080715154721.59e1db2c.sfr@canb.auug.org.au>

At Tue, 15 Jul 2008 15:47:21 +1000,
Stephen Rothwell wrote:
> 
> Hi Takashi,
> 
> Today's linux-next merge of the sound tree got a conflict in
> sound/soc/pxa/pxa2xx-i2s.c between commit
> 5a2cc50f166babc26103279c4fbc9f2bf73b79de ("[ARM] 5063/1: pxa: add clk
> support for pxa2xx I2S") from Linus' tree and commit
> a0386ed67f59f89f14dca2955ca053e81f2b75a8 ("ALSA: asoc: pxa - merge
> structs snd_soc_codec_dai and snd_soc_cpu_dai") from the sound tree
> (which is also in Linus' tree).
> 
> This is probably just a slightly different version of a conflict that has
> been in linux-next for some time.
> 
> I just added the section from Linus' tree.
> (The conflict is below)

I already rebased my tree to the latest Linus tree, and there was no
conflict indeed.  So, simply drop sound tree from linux-next for today
:)  The merge on tomorrow should be fine.


Thanks,

Takashi

> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
> 
> diff --cc sound/soc/pxa/pxa2xx-i2s.c
> index 8f96d87,9c06553..0000000
> --- a/sound/soc/pxa/pxa2xx-i2s.c
> +++ b/sound/soc/pxa/pxa2xx-i2s.c
> @@@ -80,10 -78,6 +80,13 @@@ static int pxa2xx_i2s_startup(struct sn
>   {
>         struct snd_soc_pcm_runtime *rtd = substream->private_data;
>         struct snd_soc_dai *cpu_dai = rtd->dai->cpu_dai;
> ++<<<<<<< HEAD:sound/soc/pxa/pxa2xx-i2s.c
>  +
>  +      clk_i2s = clk_get(NULL, "I2SCLK");
>  +      if (IS_ERR(clk_i2s))
>  +              return PTR_ERR(clk_i2s);
> ++=======
> ++>>>>>>> sound/master:sound/soc/pxa/pxa2xx-i2s.c
>   
>         if (!cpu_dai->active) {
>                 SACR0 |= SACR0_RST;

  reply	other threads:[~2008-07-15  6:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  5:47 linux-next: manual merge of the sound tree Stephen Rothwell
2008-07-15  6:23 ` Takashi Iwai [this message]
2008-07-15  7:15   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-09-01  4:20 Stephen Rothwell
2008-09-01  4:36 ` David Miller
2008-09-01  5:53   ` Takashi Iwai
2008-09-01  8:28     ` David Miller
2008-09-01  8:34       ` Takashi Iwai
2008-09-01  9:03         ` Stephen Rothwell
2008-09-01  9:26           ` Takashi Iwai
2008-09-01  9:44         ` David Miller
2008-12-15  4:25 Stephen Rothwell

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=s5hk5fnwtr5.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --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