All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Calfee <stevecalfee@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: git trees
Date: Wed, 30 Mar 2011 18:03:41 -0700	[thread overview]
Message-ID: <4D93D2ED.9040302@gmail.com> (raw)
In-Reply-To: <20110331003327.GF21487@opensource.wolfsonmicro.com>

On 03/30/11 17:33, Mark Brown wrote:
> On Wed, Mar 30, 2011 at 05:19:30PM -0700, Steve Calfee wrote:
> 
>> I am starting to look at a new codec driver. I have been looking at the
>> alsa-project wiki describing the various git trees. I am confused
>> because they seem to be lagging the linux releases (ie 2.6.38 is out,
>> not in the two trees I have tried.
> 
> You should be developing against the Linux kernel, not against the out
> of tree ALSA, for ASoC.  This is mostly true for regular ALSA drivers
> too.
> 

Hi Mark,

Thanks for your time. I was already using linux-next - So that would be
the correct tree when you say linux kernel?

If linux-next is the case how long do I have to wait until some of the
latest asoc patches arrive? I thought that the alsa trees were somewhat
ahead of the linux-next because they had asoc/alsa patches in them. For
instance you have patches against both 2.6.39 and 2.6.40 somewhere and I
don't think they are in linux-next.

Regards, Steve

  reply	other threads:[~2011-03-31  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31  0:19 git trees Steve Calfee
2011-03-31  0:33 ` Mark Brown
2011-03-31  1:03   ` Steve Calfee [this message]
2011-03-31 21:39     ` 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=4D93D2ED.9040302@gmail.com \
    --to=stevecalfee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.