linux-kernel - Re: linux-next: manual merge of the sound tree with the s5p tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Dec 2010 12:17:52 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Kukjin Kim <kgene.kim@...sung.com>
Cc:	'Stephen Rothwell' <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	'Jassi Brar' <jassi.brar@...sung.com>
Subject: Re: linux-next: manual merge of the sound tree with the s5p tree

At Thu, 23 Dec 2010 20:11:56 +0900,
Kukjin Kim wrote:
> 
> Takashi Iwai wrote:
> > 
> > At Thu, 23 Dec 2010 19:31:12 +0900,
> > Kukjin Kim wrote:
> > >
> > > Stephen Rothwell wrote:
> > > >
> > > > Hi Takashi,
> > > >
> > > > Today's linux-next merge of the sound tree got a conflict in
> > > > sound/soc/samsung/smdk_wm8580.c sound/soc/samsung/smdk_wm9713.c
> between
> > > > commit 7ca825bed699c77b218ead402202df384556950b ("ASoC: Samsung:
> Rename
> > > > DMA device") from the s5p tree and various commits from the sound
> tree.
> > > >
> > > > I used the versions from the sound tree that seemed to be supersets of
> > the
> > > > ones from the s5p tree.
> > >
> > > Merry Xmas Stephen :-)
> > >
> > > Thanks for your information.
> > >
> > > As I said to Mark, I did 'cherry-pick' following 2 commits in my tree
> for
> > > avoiding build error from sound-2.6.git.
> > > I couldn't 'merge' into my tree because there is no suitable branch in
> your
> > > tree...
> > >
> > > --
> > >
> > > commit 83e37b8e400ca51cc97946815b3055daacd92fa8
> > > Author: Jassi Brar <jassi.brar@...sung.com>
> > > Date:   Mon Nov 22 15:35:53 2010 +0900
> > >
> > >     ARM: Samsung: Define common audio-dma device
> > >
> > >     The ASoC uses common DMA driver for Audio devices. So it makes
> > >     sense to a common audio-dma device shared across all platforms.
> > >
> > >     Signed-off-by: Jassi Brar <jassi.brar@...sung.com>
> > >     Acked-by: Kukjin Kim <kgene.kim@...sung.com>
> > >     Acked-by: Liam Girdwood <lrg@...mlogic.co.uk>
> > >     Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> > >
> > > commit 58bb4072132c54d832082cc6eac396a6db009cbd
> > > Author: Jassi Brar <jassi.brar@...sung.com>
> > > Date:   Mon Nov 22 15:35:50 2010 +0900
> > >
> > >     ASoC: Samsung: Rename DMA device
> > >
> > >     Some Samsung SoCs have a PCM(DSP) controller. So the name
> > >     s3c24xx-pcm-audio for DMA driver is not very appropraite.
> > >     This patch moves :-
> > >         s3c24xx-pcm-audio -> samsung-audio
> > >
> > >     Signed-off-by: Jassi Brar <jassi.brar@...sung.com>
> > >     Acked-by: Kukjin Kim <kgene.kim@...sung.com>
> > >     Acked-by: Liam Girdwood <lrg@...mlogic.co.uk>
> > >     Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> > >
> > > --
> > >
> > > Maybe happened conflict from latter commit.
> > >
> > > Anyway I need above commits from sound-2.6.git in my tree...
> > > so how method is better to me instead of cherry-pick it?
> > 
> > You can merge topic/asoc branch of sound git tree.
> > This brach contains the all necessary commits for ASoC and is almost
> > never rebased.
> 
> Hi,
> 
> But I can't merge it because there is no 'topic/asoc' branch in
> sound-2.6.git.
> (git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git)
> 
> Is there another repository?

OK, Mark's tree doesn't contain.  But you can merge for-2.6.38 tree there.

The main sound git tree is found in
    git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git

> And should I merge it in my tree even though don't need all of ASoC commits
> :-( ?

In general yes because this is the tree to be merged to 2.6.38.

> I'm not sure how many commits are in there...

You can keep two branches.  One contains only your fixes, and another
is the merged branch from yours and from sound git tree.  Expose the
latter merged tree for linux-next.

There are many other ways to manage such things, but the above has
worked for me well, at least.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/