From: Piotr Hosowicz <piotr@hosowicz.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
"'Takashi Iwai'" <tiwai@suse.de>,
"'Stephen Rothwell'" <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Jassi Brar'" <jassi.brar@samsung.com>
Subject: Re: linux-next: manual merge of the sound tree with the s5p tree
Date: Thu, 23 Dec 2010 12:54:26 +0100 [thread overview]
Message-ID: <4D133872.5050804@example.com> (raw)
In-Reply-To: <20101223115024.GA28928@sirena.org.uk>
On 23.12.2010 12:50, Mark Brown wrote:
>> Is there another repository?
>
> topic/asoc is in Takashi's tree and is equivalent to my for-next branch,
> it usually lags it by only a small amount. Takashi's tree is at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
Each time I get source from Linus tree I get alsa source from Takashi
and build the kernel. Should I get the source also from you to be up to
date with sound source?
Regards and Merry Christmas,
Piotr Hosowicz
--
Babcia rox! :
alek: przyszli do mnie jehowi dzisiaj, otworzyła babcia
pate_q: i co?
alek: po 30 minutach rozmowy chcieli przejść na chrześcijaństwo
NP: Peter Green Splinter Group - Hiding In Shadows
NB: 2.6.37-rc7
next prev parent reply other threads:[~2010-12-23 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 0:53 linux-next: manual merge of the sound tree with the s5p tree Stephen Rothwell
2010-12-23 10:31 ` Kukjin Kim
2010-12-23 11:03 ` Takashi Iwai
2010-12-23 11:11 ` Kukjin Kim
2010-12-23 11:17 ` Takashi Iwai
2010-12-23 11:28 ` Kukjin Kim
2010-12-23 14:30 ` Takashi Iwai
2010-12-24 1:32 ` Kukjin Kim
2010-12-24 8:27 ` Russell King
2010-12-28 2:24 ` Kukjin Kim
2010-12-28 15:39 ` Mark Brown
2010-12-28 16:23 ` Russell King
2010-12-28 16:40 ` Mark Brown
2010-12-30 0:54 ` Kukjin Kim
2010-12-23 11:50 ` Mark Brown
2010-12-23 11:54 ` Piotr Hosowicz [this message]
2010-12-23 11:56 ` Mark Brown
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=4D133872.5050804@example.com \
--to=piotr@hosowicz.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassi.brar@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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