From: Takashi Iwai <tiwai@suse.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: linux-next: manual merge of the sound tree with the Linus' tree
Date: Mon, 06 Dec 2010 09:02:24 +0100 [thread overview]
Message-ID: <s5hpqtftjlb.wl%tiwai@suse.de> (raw)
In-Reply-To: <w3pd3pfg01p.wl%kuninori.morimoto.gx@renesas.com>
At Mon, 06 Dec 2010 10:30:44 +0900,
Kuninori Morimoto wrote:
>
>
> Dear Stephen, Takashi, Paul
>
> > Today's linux-next merge of the sound tree got a conflict in
> > sound/soc/sh/fsi.c between commit
> > d4bc99b977e3a1dd10a84a01ebe59ac2ccebf0cd ("ARM: mach-shmobile: ap4evb:
> > FSI clock use proper process for HDMI") from Linus' tree and commit
> > 2b0e73025f74699e9cc9df60649fcc14cd02481b ("ASoC: sh: fsi: change
> > fsi->mst_ctrl to master->a/b_mclk") from the sound tree.
> (snip)
> > diff --cc sound/soc/sh/fsi.c
> > index 4c2404b,19a2f99..0000000
> > --- a/sound/soc/sh/fsi.c
> > +++ b/sound/soc/sh/fsi.c
> > @@@ -131,10 -142,6 +142,8 @@@ struct fsi_priv
> >
> > struct fsi_stream playback;
> > struct fsi_stream capture;
> > +
> > + long rate;
> > -
> > - u32 mst_ctrl;
> > };
> >
> > struct fsi_core {
>
> Oops. I'm so sorry.
> I didn't care about this conflict. sorry again.
Don't worry, such a conflict isn't your fault, but happens rather
occasionally in everywhere :)
> Above fixup is excellent
Thanks for checking!
Takashi
prev parent reply other threads:[~2010-12-06 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 0:35 linux-next: manual merge of the sound tree with the Linus' tree Stephen Rothwell
2010-12-06 1:30 ` Kuninori Morimoto
2010-12-06 8:02 ` 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=s5hpqtftjlb.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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